What are the risks of connecting to npm:@apogeoapi/mcp?

References sensitive file paths / environment secrets. Overall trust grade C- (70/100).

When was npm:@apogeoapi/mcp last audited?

Last checked 2026-06-03; wmcp.sh re-checks it on a schedule for tool drift and rug-pulls.

C-

npm:@apogeoapi/mcp

Item: npm:@apogeoapi/mcp
Rating: 70
Author: wmcp.sh

https://www.npmjs.com/package/@apogeoapi/mcp

70/100 · MCP Trust Grade · checked 1mo ago · MCP 1.0.2

Is the npm:@apogeoapi/mcp MCP server safe to use?

Independent trust grade C- (70/100). References sensitive file paths / environment secrets. wmcp.sh continuously watches npm:@apogeoapi/mcp for tool drift and rug-pulls. The grade is free and identical whether or not the operator pays.

What it offers — 6 tools · Maps & Geo

get_cities

Get all cities for a state/province by state ID. Requires Starter plan or above.

get_country

Get full data for a country by ISO2 or ISO3 code — includes name, capital, region, population, currency, live USD exchange rate, timezones, and phone

list_countries

List all countries with pagination. Returns basic info by default — add fields=full for all data.

search_countries

Search countries by name (e.g.

get_currency_rate

Get the live USD exchange rate for a country\

geolocate_ip

Geolocate an IPv4 or IPv6 address — returns country, region, city, coordinates, timezone, and EU membership. Requires Starter plan or above.

Spec / packaging20%100

✓ depends on an MCP SDK
✓ declares a bin entry (runnable server)
✓ 6 tool(s) detected in source

Security (OWASP MCP)30%25

⚠ references sensitive file paths / env secrets
scanned 6 source files

Maintenance / popularity20%92

published within 90 days
3 published versions

Tool hygiene15%70

no TypeScript types
2 runtime deps

Transparency / provenance15%90

✓ public repository linked
✓ MIT license

Findings

WARNMCP08 References sensitive file paths / environment secrets.

INFO Static analysis of npm package @apogeoapi/mcp@1.0.2 (stdio server — no remote endpoint). Reliability/behavioral signals require running it; not measured.

Grade another server

We re-grade npm:@apogeoapi/mcp on a schedule and alert your Slack/webhook the moment its tools change or its grade drops — rug-pull insurance for the connection.

Share this report card

A 1200×630 card with the grade + audit — drop it in a post, Slack, or your repo.

MCP Trust report card — npm:@apogeoapi/mcp grade C-

Share on X Open card image

https://wmcp.sh/mcp/grade/npm%3A%40apogeoapi%2Fmcp

Embed this grade

A live badge — it re-verifies itself and shows current stability. Static scorecards can't. Paste it in your README or site to show users you're independently audited.

Markdown (for your README)

[![MCP Trust Grade C-](https://wmcp.sh/mcp/grade/npm%3A%40apogeoapi%2Fmcp/badge.svg)](https://wmcp.sh/mcp/grade/npm%3A%40apogeoapi%2Fmcp)

HTML

<a href="https://wmcp.sh/mcp/grade/npm%3A%40apogeoapi%2Fmcp"><img src="https://wmcp.sh/mcp/grade/npm%3A%40apogeoapi%2Fmcp/badge.svg" alt="MCP Trust Grade C- · wmcp.sh"></a>

Agents: check this before connecting

Add the wmcp.sh trust oracle as an MCP server and call grade_mcp_server / check_mcp_drift in your agent's pre-connection gate:

https://wmcp.sh/mcp/trust

How this grade is computed. An open, independent rubric — Spec conformance (20%), Security mapped to the OWASP MCP Top 10 (30%), Reliability (20%), Tool hygiene (15%), Transparency (15%) — run by connecting to the server and inspecting its real MCP surface. The grade is free and identical whether or not the operator pays. v1 uses static + spec signals from a single connection; continuous uptime, real latency, and annotation-truthing (declared readOnly vs observed behavior) layer on via the wmcp.sh proxy.