mcp-registry/cc.scopeai/geo-observation · v0.2.1
As of 2026-10-26 10:22 UTC, the Scopeai Geo Observation MCP server is up with a Glimind reliability score of 96/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.
GEO brand visibility and AI citation evidence. Free capability discovery and request matching.
Claude Code
claude mcp add --transport http scopeai-geo-observation-mcp-server https://scopeai.cc/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"scopeai-geo-observation-mcp-server": {
"type": "http",
"url": "https://scopeai.cc/mcp"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
44 parameter(s) across 9 tool(s) have no description.
Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →
No tool declares an outputSchema.
Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →
Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/cc.scopeai/geo-observation"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/cc.scopeai/geo-observation"}) over MCP.
geo_create_project ~853 tokensgeo_prepare_optimization ~412 tokensgeo_quote_observation ~392 tokensgeo_match_request ~350 tokensgeo_accept_observation ~330 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fcc.scopeai%2Fgeo-observation?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fcc.scopeai%2Fgeo-observation?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fcc.scopeai%2Fgeo-observation.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fcc.scopeai%2Fgeo-observation.svg :target: https://glimind.com/server/mcp-registry%2Fcc.scopeai%2Fgeo-observation?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:d83d0227e55f3c21…, first seen 2026-10-17, included at leaf 7517 of 72,181. Version history · verify what your client received.
Compare: most reliable payments servers · most reliable other servers · most reliable knowledge servers · most reliable data servers · most reliable retrieval servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-26 10:22 UTC, the Scopeai Geo Observation MCP server is up with a Glimind reliability score of 96/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.
Scopeai Geo Observation MCP server advertises 11 tools, including geo_accept_observation, geo_cancel_observation, geo_create_project, geo_describe_service, geo_get_answers.
Point your MCP client at this streamable-http endpoint: https://scopeai.cc/mcp
Glimind scanned all 11 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.