// v2 · MCP interface

MCP interface

Fastah runs a remote Model Context Protocol (MCP) server that gives AI agents IP context: the approximate location and network of an IP address. Network operators can also use it to check the place names in RFC 8805 geofeed rows.

Connection details

SettingValue
Server URLhttps://mcp.fastah.ai/mcp
TransportStreamable HTTP, stateless (the server issues no session IDs)
Protocol revision2026-07-28
AuthenticationWorkOS AuthKit bearer token, through anonymous agent registration or signed-in OAuth; issuer https://signin.fastah.net
API keysNot accepted. Fastah API keys and v2 API bearer tokens do not work on the MCP server.

Try without a user account

Anonymous agent registration gives your agent the read-only fastah:mcp:read permission without an email address or a user sign-in. Anonymous does not mean unauthenticated: every MCP request still needs a bearer token.

Follow the agent registration instructions for the maintained commands and secure credential storage:

  1. Reuse an existing registration if you have one. Otherwise, register an anonymous identity at https://signin.fastah.net/agent/identity.
  2. Exchange identity.assertion at https://signin.fastah.net/oauth2/token using the JWT-bearer grant (urn:ietf:params:oauth:grant-type:jwt-bearer) and resource https://mcp.fastah.ai/mcp.
  3. Send the returned access token privately in Authorization: Bearer. Do not paste assertions or tokens into prompts, logs, screenshots or source control.

The access token lasts 24 hours and does not renew automatically. Manually exchange the same assertion for another token while the assertion is valid. An unclaimed anonymous assertion lasts three days; after it expires, register again. The trial itself does not end just because one access token expires.

You can later claim the identity through the registration instructions, or use signed-in OAuth below. Anonymous access grants the read-only MCP permission, not broader account access.

Signed-in OAuth access

Your MCP client handles sign-in for you, if it supports OAuth for remote servers:

  1. The client calls the server URL without a token. The server answers 401 with WWW-Authenticate: Bearer resource_metadata="https://mcp.fastah.ai/.well-known/oauth-protected-resource".
  2. That document names https://signin.fastah.net as the authorization server. The client discovers its endpoints and registers itself.
  3. A browser window opens. Sign in and approve access.
  4. The client requests the resource https://mcp.fastah.ai/mcp and sends the token it receives in an Authorization: Bearer header.

To see the discovery document yourself:

bash
curl https://mcp.fastah.ai/.well-known/oauth-protected-resource

Tools

Both tools are read-only.

ip-to-geolocation-attributes

Returns public-internet attributes for IP addresses: approximate location with an accuracy radius, city, region, country and time zone. Pass a single ip, or an ips array of up to 1,000 addresses. Batch results come back in input order, and a failure for one address is reported inline without failing the batch.

IP-derived locations are approximate. They are not proof of identity or of an exact physical location.

rfc8805-row-place-search

Suggests places for the location fields of RFC 8805-shaped rows, so you can check a geofeed's country, region and city names before you publish it. Send 1 to 1,000 rows. Each row has only these fields:

  • rowKey: an opaque key, 32 to 128 characters, unique within the batch, that you use to match results to your rows;
  • countryCode: an ISO 3166-1 alpha-2 code, empty, or ZZ;
  • optional regionCode in ISO 3166-2 CC-SUB form, matching countryCode;
  • optional cityName;
  • optional searchMode: auto, prefer_larger_area or prefer_larger_population_center.

Never put an IP prefix, a feed URL, your organization's name or registry data in any field. The tool only needs the location text.

Every row gets one result, in input order, with a status: matched, do_not_geolocate (an empty or ZZ country, which asks consumers not to geolocate the prefix), no_match, invalid_input or backend_unavailable. Matches are suggestions in best-first order, with a centre point, a bounding box and an approximate radius. The radius and the population weight help you choose between places; they are not confidence scores.

Client compatibility

Use a client that supports the server's stateless MCP revision 2026-07-28 and your chosen authentication path: a manually supplied bearer token for anonymous access, or remote-server OAuth for signed-in access.

Direct HTTP tool calls are verified in production. A configuration command alone is not proof of compatibility. There is no API-key option.

Authoring geofeeds with an agent

Network operators can use the open-source tuning-geofeeds Skill. Its offline checks of a geofeed CSV work in Claude and Amp: it explains what to fix and changes only what you approve, and its README covers installing it. To confirm place names, the Skill can also call rfc8805-row-place-search, which uses this server's MCP 2026-07-28.

Related