Skip to main content
Skip to content

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
geo.qa core
5
tools, counted from tools/list when this page loaded

read_world, detect_objects, classify_land_cover, analyze_scene, verify_receipt.

https://geo.qa/api/mcp
geo.qa Fields
9
tools, counted from tools/list when this page loaded

Seasons, crop dates, flood, drought, water balance, pest risk, boundaries, validation.

https://geo.qa/mcp
emem memory
119
tools, counted from tools/list when this page loaded

Locate, recall, cite, bundle and verify signed Earth facts; shared notes between agents.

https://emem.dev/mcp

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.

tools/list request in progress…

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".

# Every route, in the service's own words:
curl -s https://geo.qa/api/partner
Discovery files
A2A agent card
/.well-known/agent-card.json, signed JWS
Open
Protected resource metadata
/.well-known/oauth-protected-resource, RFC 9728
Open
Root of trust
/.well-known/geoqa.json, ed25519 key
Open

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.

TierYou presentYou get
verifynothingRe-check any receipt, fetch the keys, read the transparency log.
readnothingread_world, detect_objects and tools/list on the MCP endpoint.
keyedAuthorization: Bearer on_…The metered tools: land cover, scene analysis, tenancy reads.
signed ina geo.qa sign-in (OAuth 2.1, at https://geo.qa/api/mcp/account) or an API keyThe metered tools too: land cover and scene description, counted against your plan.
subscriptiona plan from /pricingMonthly in INR through Razorpay, or an invoice.
tenancyan organisation agreementYour 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.