smithery runs an MCP server that responds but requires authentication. We can confirm the endpoint exists and answers; we cannot see what it exposes, so no tool list appears below. That is a reasonable thing to do with a private server, and it is not a fault. First seen on 17 September 2026.
| Endpoint | Type |
|---|---|
| Composioauth required Manage Composio tools, connected accounts, MCP servers, triggers, and webhooks. Requires an API key from the Composio dashboard. endpoint: https://server.smithery.ai/smithery/composio/mcpidentifier: urn:air:smithery:mcp:composiomcp smithery remote | application/mcp-server-card+json |
| Notionanswers in 328ms Manage your workspace by searching, creating, and updating pages or databases. Access team information, user profiles, and comments across your organization. Organize documents efficiently by moving and duplicating content seamlessly. endpoint: https://server.smithery.ai/smithery/notion-test/mcpidentifier: urn:air:smithery:mcp:notion-testmcp smithery remote | application/mcp-server-card+json |
| Smitheryauth required Discover, deploy, and manage MCP servers on Smithery. Browse the registry, manage server deployments, releases, secrets, and team API keys, and run skills. endpoint: https://server.smithery.ai/smithery/mcpidentifier: urn:air:smithery:mcp:smitherymcp smithery remote | application/mcp-server-card+json |
https://neuronto.com/search, or connect an agent to https://neuronto.com/mcp.
If this is your domain, the free console shows what a registry
sees when it reads your manifest. To hear when any of it changes,
publisher
monitoring is $19 a month, the first 14 days free.