Geo (rickycambrian) MCP Server
geo-mcp-server
npm
v1.8.0
Published by rickycambrian — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.
MCP server providing full access to the Geo protocol SDK for knowledge graph operations
The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.
1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:
The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.
2. Client adoption risk — 100 − 4 = 96. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:
| Points | Adoption-risk factor |
|---|---|
| −3 | capability blast radius (moderate) — client exposure if the model is manipulated |
| −1 | publisher verification (public source) — no provenance, but the source is public and inspectable |
Capability observations and info notes are shown under Findings but never scored.
Open any row's finding below for the file, line and evidence behind a deduction.
Findings 0
Tools 44
Each tool and what it can reach — statically extracted from the published source.
get_page_contentingests untrusted inputadd_values_to_entityno sensitive capabilitybuild_schemano sensitive capabilityclear_sessionno sensitive capabilityconfigure_walletno sensitive capabilitycreate_entityno sensitive capabilitycreate_imageno sensitive capabilitycreate_knowledge_graphno sensitive capabilitycreate_knowledge_graph_from_fileno sensitive capabilitycreate_propertyno sensitive capability
Show 34 more tools ↓
create_relationno sensitive capabilitycreate_research_ontology_paper_and_claimsno sensitive capabilitycreate_research_paper_and_claimsno sensitive capabilitycreate_typeno sensitive capabilitydelete_entityno sensitive capabilitydelete_relationno sensitive capabilitydelete_workspace_entityno sensitive capabilitygenerate_idno sensitive capabilityget_entityno sensitive capabilityget_proposalno sensitive capabilityget_proposal_votesno sensitive capabilityget_proposalsno sensitive capabilityget_session_statusno sensitive capabilityget_spaceno sensitive capabilityget_system_idsno sensitive capabilityget_typeno sensitive capabilitylist_entitiesno sensitive capabilitylist_spacesno sensitive capabilitylist_typesno sensitive capabilitypropose_accept_editorno sensitive capabilitypropose_accept_subspaceno sensitive capabilitypropose_dao_editno sensitive capabilitypropose_remove_editorno sensitive capabilitypropose_remove_subspaceno sensitive capabilitypublish_editno sensitive capabilityread_local_fileno sensitive capabilityresolve_workspace_entitiesno sensitive capabilitysearch_entitiesno sensitive capabilitysetup_spaceno sensitive capabilitysubmit_signed_transactionno sensitive capabilityupdate_entityno sensitive capabilityupsert_canvas_workflowno sensitive capabilityupsert_workspace_entityno sensitive capabilityvote_on_proposalno sensitive capability
What this scan could not see
- Tools were statically extracted from the published source (44 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
Versions 1
Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.
| Version | Score | Findings | Engine | Scanned |
|---|---|---|---|---|
v1.8.0 latest |
A 96/100 | 0 | 1.13.0 | 2026-09-07 |
Embed this score
Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.
Verify this score yourself
The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.
npx mcptrustchecker scan geo-mcp-server --onlineOther implementations of Geo 6
Independent packages implementing the same tool, scanned with the same engine. Compare all 7 side by side →
Connect your AI to geocoding, routing, traffic, weather, and place search — 11 tools via MCP.
MCP Server for coordinate conversion and spatial calculations
Geospatial MCP server — give AI agents geocoding, routing, spatial ops, and OSM querying via the Model Context Protocol
A Model Context Protocol (MCP) server for accessing GEO (Gene Expression Omnibus) data through NCBI E-Utils API
MCP Server for generating precise geometric images using Asymptote.
Security scan results for the Geo (npm) MCP server.
More in Finance & Commerce
<img src="./public/logo.png" alt="1Money Logo" width="200"/>
Signed verification attestations for agent decisions: business, price, freshness, claim checks.
Actual Budget MCP server exposing API functionality
MCP server for Actual Budget - query and manage your personal finances through Claude
The Adyen Model Context Protocol server allows you to integrate with Adyen APIs through LLMs function calling utilizing various Clients. It currently supports the following tools:
Trusted agent-commerce hub: discover, trust-check, and route x402 payments with failover.