Home › Verified on MCPwell
What Verified on MCPwell Means
Verified on MCPwell means one thing: on 2026-10-17, a read-only check against that server's public HTTPS URL returned an initialize result and then a tools/list result. The check uses the same two methods as the tester. It does not send tools/call. It does not send a token, a cookie, or any other credential. The SVG shows that date and the number of tools in the response.
The check runs from MCPwell, not in your browser. The browser tester can still fail if the server does not send CORS headers. A pass here is not a test inside Claude, Cursor, or VS Code, and it is not a review, a ranking, or a promise about uptime.
On 2026-10-17 this check was run against 19 public HTTPS URLs taken from fact sheets. 6 returned both results. 13 returned HTTP 401 and are not verified. This was not a scan of every server in the directory. Nineteen public HTTPS URLs from fact sheets. Not a scan of the full directory. Same two methods as the on-site tester: initialize, then tools/list. No tools/call and no credentials.
Passed
- cloudflare — MCPwell · verified 2026-10-17 · 2 tools. URL
https://docs.mcp.cloudflare.com/mcp. - context7 — MCPwell · verified 2026-10-17 · 2 tools. URL
https://mcp.context7.com/mcp. - exa — MCPwell · verified 2026-10-17 · 2 tools. URL
https://mcp.exa.ai/mcp. - firecrawl — MCPwell · verified 2026-10-17 · 3 tools. URL
https://mcp.firecrawl.dev/v2/mcp. - draw-io — MCPwell · verified 2026-10-17 · 3 tools. URL
https://mcp.draw.io/mcp. - compiler-explorer — MCPwell · verified 2026-10-17 · 7 tools. URL
https://godbolt.org/mcp.
Checked, not verified
- figma — HTTP 401 from
https://mcp.figma.com/mcp. Not verified. - github — HTTP 401 from
https://api.githubcopilot.com/mcp/. Not verified. - notion — HTTP 401 from
https://mcp.notion.com/mcp. Not verified. - stripe — HTTP 401 from
https://mcp.stripe.com. Not verified. - supabase — HTTP 401 from
https://mcp.supabase.com/mcp. Not verified. - sentry — HTTP 401 from
https://mcp.sentry.dev/mcp. Not verified. - linear — HTTP 401 from
https://mcp.linear.app/mcp. Not verified. - atlassian — HTTP 401 from
https://mcp.atlassian.com/v2/mcp. Not verified. - canva — HTTP 401 from
https://mcp.canva.com/mcp. Not verified. - neon — HTTP 401 from
https://mcp.neon.tech/mcp. Not verified. - posthog — HTTP 401 from
https://mcp.posthog.com/mcp. Not verified. - vercel — HTTP 401 from
https://mcp.vercel.com. Not verified. - webflow — HTTP 401 from
https://mcp.webflow.com/mcp. Not verified.
The badge image exists only for a URL that passed. An unknown /badge/ name is a 404. Maintainer markup, when a server passed, is on that fact sheet.
Related: MCP security checklist, tester, client setup.
FAQ
What does Verified on MCPwell mean?
On 2026-10-17, initialize and tools/list both returned a result for that public HTTPS URL. The check sends no credential and does not call a tool.
Why is Figma not verified?
The check sent initialize to https://mcp.figma.com/mcp with no credential on 2026-10-17. The status was HTTP 401. That is not a successful check, so there is no badge and no tools/list snapshot.
Does the badge mean the server is safe?
No. It records that those two read-only methods succeeded on that date, and how many tools came back. The security checklist is a separate page.