Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add gaopengbin/cesium-mcp/plugin install cesium-mcpWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/mcp/gaopengbin/cesium-mcp/cesium)<a href="https://agentmods.dev/mcp/gaopengbin/cesium-mcp/cesium"><img src="https://agentmods.dev/badge/mcp/gaopengbin/cesium-mcp/cesium.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
cesium scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 7d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
{
"cesium": {
"type": "stdio",
"command": "node",
"args": [
"${CLAUDE_PLUGIN_ROOT}/packages/cesium-mcp-runtime/dist/cli.js"
],
"env": {
"CESIUM_TOOLSETS": "all",
"CESIUM_WS_PORT": "9100",
"CESIUM_ION_TOKEN": ""
}
}
}What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 7d ago First seen · 14 lines scan A 3849c4c88f40
cesium is an MCP server published in the GitHub repository gaopengbin/cesium-mcp (135 stars, last pushed today), licensed MIT. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other mcp servers, from other repositories
geolens
Apache-2.0 read-only Model Context Protocol (MCP) server for GeoLens. Lets coding agents discover datasets, inspect schemas, and ask spatial questions against any GeoLens instance. Runs locally from the geolens-mcp Python package. Needs 3 environment variables to run.
infranode
Keyless open data for 84 German cities: 12 lean read-only MCP tools covering 67 data types. Remote server at mcp.infranode.dev.
godot-mcp
MCP server "godot-mcp" as configured in sandraschi/godot-mcp. Launched with https://github.com/sandraschi/godot-mcp/releases/download/v0.5.0-beta.1/godot-mc.
osm-edit
Review-first MCP server for previewed, version-checked OpenStreetMap road edits from local GPX surveys. Runs locally from the osm-edit-mcp Python package. Needs 3 environment variables to run.
placeroot
Ground AI agents in open map data. MCP server for Overture Maps — compact answers, no API key. Runs locally from the placeroot Python package. Needs 1 environment variable to run.
stellavault
Drop anything. It compiles itself into knowledge. Claude remembers everything you know. Local-first MCP server, vault files never modified. Runs locally from the stellavault npm package.