io.metricport/metricport
MetricPort
Is the MetricPort MCP server down? No. It is up and needs auth (HTTP 401), probed 2026-11-15.
Google Search Console, Ads and AdSense analytics for AI clients. Hosted, read-only, 57 tools.
needs auth probed 2026-11-15 · HTTP 401 · Bearer
Streamable HTTP error: Error POSTing to endpoint: {"error":"invalid_token","error_description":"No authorization provided"}- Endpoint
- https://metricport.io/api/mcp (streamable-http)
- Host
- metricport.io
- Package
- The publisher's package npm:metricport-mcp did not list its tools in the container: needs network, MCP error -32000: Connection closed syscall: 'getaddrinfo', hostname: 'metricport.io' } }.
- Getting access
- OAuth with dynamic client registration. A client such as Claude Code, Cursor or npx mcpcost auth https://metricport.io/api/mcp registers itself and opens the consent page; the publisher has nothing to set up for you.
Authorization server clerk.metricport.io, PKCE S256, grants authorization_code, refresh_token, urn:ietf:params:oauth:grant-type:device_code.
Scopes profile email.
Read from the server's public OAuth metadata, without a token. Method. - Repository
- https://github.com/MinerSimonDev/metricport-mcp
- Website
- https://metricport.io
- Registry
- active, updated 2026-10-18 · registry entry
Compare this server with others.
More servers
Servers that mention analytics or adsense.
- JustIdea Agency agency.justidea/justidea-agency · alive
- Alpic ai.alpic.mcp/alpic-mcp · needs auth
- Analytics Legends — SAP AI & Analytics MCP Server ai.analyticslegends/sap-analytics · alive
- AutoRFP.ai ai.autorfp/mcp · needs auth
- AwrAIter — Telegram channels ai.awraiter/telegram · needs auth
- Web Analytics ai.b77/web-analytics · needs auth
- BAMF.ai ai.bamf/bamf · not MCP
- Eevy ai.eevy/mcp · needs auth
Badge for the README
The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.
A mail when this server changes
Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.
For the publisher
- The server answers HTTP 401 to an unauthenticated initialize, so the probe cannot list its tools. That is correct for a private server. Some public servers answer initialize and tools/list without credentials and ask for auth on tool calls only; those get a token count here.
Fixed something? Probe it now, with the same steps as the daily run. This page updates with the next daily run.