Geo MCP Server
Related Servers
Alternatives to Geo MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables AI agents to retrieve compact, evidence-backed knowledge graph packets, verify claims against sourced provenance, trace cryptographic audit trails, and explore entity relationships while minimizing context token usage.1218 npm1MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to participate in a decentralized network, earn GSTD tokens by performing computational tasks, and communicate via the A2A protocol.2MIT
- AlicenseBqualityBmaintenanceEnables building and querying vector-based knowledge graphs with node and edge management and semantic search.56 npm21 PyPIMIT
- AlicenseAqualityDmaintenancePowers AI agents with indexed blockchain data from The Graph, enabling them to fetch subgraph schemas and execute GraphQL queries against blockchain data.29MIT
- AlicenseAqualityBmaintenanceEnables AI agents to access verifiable DePIN supply-side telemetry, browse and purchase data products using credits, query datasets, and verify data provenance with cryptographic and zero-knowledge tools.1057 npmMIT

@ainize/mcpofficial
AlicenseNot gradedqualityBmaintenanceEnables AI agents to search, verify, purchase, and teach knowledge through a decentralized knowledge marketplace, with strict spending limits and secret management.MIT
TDQS
Scored across 44 tools
Multiple tools have unclear boundaries, especially create_research_paper_and_claims vs create_research_ontology_paper_and_claims, which appear to do nearly the same thing. High-level builders like create_knowledge_graph and build_schema overlap with granular create_property/create_type/create_entity, and upsert_canvas_workflow vs upsert_workspace_entity are easy to confuse. The descriptions help, but an agent could easily pick the wrong level or duplicate function.
The vast majority of tools follow a clear snake_case verb_noun pattern, such as create_entity, list_spaces, delete_relation, and get_proposal. Minor deviations like create_knowledge_graph_from_file, create_research_paper_and_claims, vote_on_proposal, and propose_accept_editor are still readable but break the simple verb_noun shape slightly.
44 tools is far beyond the typical well-scoped MCP surface and crosses the 25+ threshold for 'too many'. While the server covers several subdomains, many tools are convenience wrappers or near-duplicates, making the overall toolset feel heavy and harder to navigate.
The toolset covers most core workflows: entity CRUD, schema building, research claim creation, workspace management, and DAO proposal/voting. Gaps exist for dedicated property listing, relation reads/updates, and general proposal creation, but agents can work around these using get_entity, search_entities, and propose_dao_edit.