> ## Documentation Index
> Fetch the complete documentation index at: https://docs.mireye.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Security and server details

> What a Mireye MCP connection can reach and spend, how sign-in works, and the facts for building your own client.

## What a connection can do

For anyone approving Mireye MCP for a team.

**Access**

* The tools look data up. They do not touch your files or systems.
* One tool, `mireye_request_field`, files a request for new data. It can notify
  a webhook or email address the agent gives it.

**What Mireye sees**

* Only what the agent puts in a tool call.
* Not the rest of your conversation.
* With Mireye Agent, that includes the question the agent sends.

**What Mireye keeps**

* Each tool call: what the agent sent, and the result.
* With Mireye Agent, that includes the question and the answer.
* Addresses are kept with the result, so an answer can be audited.
* Saved paid results are kept for 30 days.
* Other retention questions? Email
  [founders@mireye.com](mailto:founders@mireye.com).

**Sign-in**

* OAuth 2.1 with PKCE. One scope: `mcp:tools`.
* The app holds a token for Mireye MCP only.
* Sign-in never gives the app your password or an API key.
* The token expires. The app renews it on its own.
* Enrich, Search and driving Proximity also need the current terms accepted on
  the sign-in page.

**Where credentials live**

* Each app stores its own token.
* Guided setup also saves an API key at
  `~/.config/mireye-mcp/credentials.json`. Only your user can read it.
* The setup prompt carries that key. The agent you paste it into sees it.

**Network**

* The app talks to `api.mireye.com` over HTTPS.
* The sign-in page is on `www.mireye.com`. Signing in with Google goes through
  Google.
* Mireye Agent table downloads are short-lived links on a separate
  file-storage host.

**Removing access**

* Remove or disconnect the server in the app.
* To revoke a sign-in on Mireye's side, email
  [founders@mireye.com](mailto:founders@mireye.com).

## What a connection can spend

* Each person signs in with their own Mireye account.
* Calls are billed to that account's prepaid balance.
* Fetch and Geocode are free.
* A paid call that costs more than the balance stops before any charge.
* Auto-recharge is off unless the account owner turns it on.

Per-call caps:

* Paid tools accept `max_cost_usd`. A call that would cost more stops before
  any charge.
* The cap is optional.

Without a cap:

| Tool | What can be spent |
| - | - |
| Enrich, Search | The listed price |
| Proximity | Up to \$10 |
| Mireye Agent | Up to the balance |

An Agent task that runs out of balance part-way:

* Charges for the steps it finished.
* Waits for funds.

## More

* API keys for the HTTP API are separate. See [Authentication](https://docs.mireye.ai/authentication.md).
* [Terms](https://www.mireye.com/terms) and
  [privacy policy](https://www.mireye.com/privacy).
* Security review or data question? Email
  [founders@mireye.com](mailto:founders@mireye.com).

## Send this to your admin

If your company controls which connectors you can add, copy this:

```text theme={null}
Request: allow the Mireye custom MCP connector

Server URL:   https://api.mireye.com/mcp
Sign-in:      OAuth 2.1 with PKCE, scope mcp:tools. Each user signs in with their own Mireye account.
Domains:      api.mireye.com (API), www.mireye.com (sign-in page). Mireye Agent table downloads use short-lived links on a separate file-storage host.
What it does: Looks up US property and location data. One tool can file a request for new data.
What it gets: What the assistant sends in a tool call (an address, coordinate, filter, or a question for Mireye Agent). No files. No chat history.
What it keeps: Each tool call and its result. Saved paid results are kept for 30 days.
Cost:         Billed per user to a prepaid Mireye balance. Fetch and Geocode are free.
Docs:         https://docs.mireye.ai/mcp/security
Contact:      founders@mireye.com
```

## Server details

For people building their own MCP client.

| | |
| - | - |
| URL | `https://api.mireye.com/mcp` |
| Transport | Streamable HTTP |
| Sign-in | OAuth 2.1 with PKCE |
| Client registration | Dynamic. Endpoints come from the server's metadata |
| Scope | `mcp:tools` |
| Redirect URLs | HTTPS, or HTTP on localhost |
| API keys | Not accepted on this URL |
| Protocol versions | `2024-11-05`, `2025-03-26`, `2025-06-18`, `2025-11-25` |
| Tool timeout, Search | At least 630 seconds |
| Tool timeout, Agent tools | More than 30 seconds |
| Registry name | `com.mireye/earth` in the official MCP registry |

Newer protocol versions:

* A client that opens with a newer version, such as `2026-07-28`, gets a `400`.
* The `400` names the versions above.
* The client should then start again with `initialize`.
* Claude Code and the MCP SDKs do this on their own.
