Make your agent cite, not invent.
32 tools listed on three MCP servers give your agent signed facts about real places, and emem holds 119 tools in all, reached through emem_tools. Each answer names its sources and carries a receipt. Reads need no key and no account.
claude mcp add --transport http geoqa https://geo.qa/api/mcp claude mcp add --transport http geoqa-fields https://geo.qa/mcp claude mcp add --transport http emem https://emem.dev/mcp
read_world, detect_objects, classify_land_cover, analyze_scene, verify_receipt.
Seasons, crop dates, flood, drought, water balance, pest risk, boundaries, validation.
Locate, recall, cite, bundle and verify signed Earth facts; shared notes between agents.
Every tool, read live from the servers.
This list is not written by hand. The page calls tools/list on each server, so it cannot drift from what your agent sees.
Pick a tool.
Fourteen HTTP routes that measure. No key.
Beside the MCP tools, geo.qa has plain HTTP routes that measure rather than retrieve. They grade produce against EU 2023/2429, count crates, remove people from a photograph, measure the distance to surface water and rank candidate farms from pins.
When a route cannot measure, it says why, by name. No scale in the frame is not a length. An unreadable pin is not a low score. An angled stack gets "retake: square_on".
The rungs an agent can climb.
A metered route never gives a dead refusal. It answers with every way to get that resource, and marks which ones a machine can take without a person.
| Tier | You present | You get |
|---|---|---|
| verify | nothing | Re-check any receipt, fetch the keys, read the transparency log. |
| read | nothing | read_world, detect_objects and tools/list on the MCP endpoint. |
| keyed | Authorization: Bearer on_… | The metered tools: land cover, scene analysis, tenancy reads. |
| signed in | a geo.qa sign-in (OAuth 2.1, at https://geo.qa/api/mcp/account) or an API key | The metered tools too: land cover and scene description, counted against your plan. |
| subscription | a plan from /pricing | Monthly in INR through Razorpay, or an invoice. |
| tenancy | an organisation agreement | Your own memory, your own keys, your own jurisdiction. |
API keys start with on_ and come from your account. REST takes Authorization: Bearer on_…; MCP takes the same value as X-API-Key. A receipt check never needs a key.