# TheAIMeters (remote · www.theaimeters.com)

Read-only AI impact metrics with search, methodology and cited sources. No authentication required.

- Trust score: 89/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `www.theaimeters.com`: 89/100 (this document), [markdown](https://verifymcp.io/servers/com-theaimeters-theaimeters/www.md), [page](https://verifymcp.io/servers/com-theaimeters-theaimeters/www)

## Channel facts

- Endpoint: `https://www.theaimeters.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 83/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 82/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 365 tokens (~73/item across 5 items; 5 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 93/100
  - Stability observed for 28 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the TheAIMeters MCP server?

TheAIMeters is a hosted endpoint at https://www.theaimeters.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http com-theaimeters-theaimeters 'https://www.theaimeters.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-theaimeters-theaimeters": {
      "url": "https://www.theaimeters.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-theaimeters-theaimeters": {
      "type": "http",
      "url": "https://www.theaimeters.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-theaimeters-theaimeters]
url = "https://www.theaimeters.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-theaimeters-theaimeters": {
      "type": "remote",
      "url": "https://www.theaimeters.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-theaimeters-theaimeters --url 'https://www.theaimeters.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-theaimeters-theaimeters:
    url: "https://www.theaimeters.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-theaimeters-theaimeters": {
      "Transport": "http",
      "Url": "https://www.theaimeters.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-theaimeters-theaimeters -t streamable-http -u 'https://www.theaimeters.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-theaimeters-theaimeters": {
      "type": "http",
      "url": "https://www.theaimeters.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-04 (score 89, +1)

No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-02 (score 88, +1)

No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-31 (score 87, +1)

No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-29 (score 86, +1)

No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-27 (score 85, +1)

No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-25 (score 84, +1)

No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-22 (score 83, +1)

No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-20 (score 82, +1)

No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (5)

### `list_meters` (~29 tokens)

List all meters as returned by the TheAIMeters API, without recalculating their values.

Output parameters:

- `meters` (array)

### `get_meter` (~86 tokens)

Get one meter by its exact slug from list_meters (not its UUID). Use this when the slug is known; this is not a text search. Returns the stored API data without recalculating values, or a tool error if the meter does not exist.

Input parameters:

- `slug` (string, required): Exact meter slug from list_meters or search_meters, for example electricity-ai-today.

Output parameters:

- `meter` (object)

### `search_meters` (~96 tokens)

Find meters when the exact slug is unknown. The backend searches for a literal, case-insensitive substring in slug, label, group and sourceNote, and orders matches by slug. This is not semantic search; no matches returns an empty meters array. Use list_meters to browse all meters.

Input parameters:

- `query` (string, required): Non-empty search text, for example water or GPU. Percent and underscore are literal characters, not wildcards.

Output parameters:

- `meters` (array)

### `get_methodology` (~96 tokens)

Explain how TheAIMeters indicators are produced. Omit slug for the general methodology and meter-to-methodology mappings. Supply an exact meter slug for its calculation, formula, assumptions, limitations, refresh policy and structured sources. Returns backend-authored content as-is; an unknown meter methodology is a tool error.

Input parameters:

- `slug` (string): Exact meter slug from list_meters or search_meters, for example electricity-ai-today.

Output parameters:

- `meter` (object)
- `meters` (array)
- `methodology`
- `sources` (array)

### `get_sources` (~58 tokens)

List the complete TheAIMeters source catalog with stable IDs, names, URLs and categories. Use this for an overview of references. For sources supporting one specific meter, use get_methodology with its slug. Does not fetch the referenced external websites.

Output parameters:

- `sources` (array)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-theaimeters-theaimeters/www#diagnostics

## Score history

- 2026-11-05: 89
- 2026-11-04: 89
- 2026-11-03: 88
- 2026-11-02: 88
- 2026-11-01: 87
- 2026-10-31: 87
- 2026-10-30: 86
- 2026-10-29: 86
- 2026-10-28: 85
- 2026-10-27: 85
- 2026-10-26: 84
- 2026-10-25: 84
- 2026-10-24: 83
- 2026-10-23: 83
- 2026-10-22: 83
- 2026-10-21: 82
- 2026-10-20: 82
- 2026-10-19: 81
- 2026-10-18: 81
- 2026-10-17: 80
- 2026-10-16: 80
- 2026-10-15: 79
- 2026-10-14: 79
- 2026-10-13: 78
- 2026-10-12: 78
- 2026-10-10: 77
- 2026-10-08: 76

## Common questions

### What is the TheAIMeters MCP server?

TheAIMeters is an MCP server listed in the public MCP registry as com.theaimeters/theaimeters. Read-only AI impact metrics with search, methodology and cited sources. No authentication required. This page covers its hosted endpoint (https://www.theaimeters.com/mcp).

### Is the TheAIMeters MCP server safe to use?

TheAIMeters scores 89 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the TheAIMeters MCP server expose?

TheAIMeters exposes 5 tools: list_meters, get_meter, search_meters, get_methodology, get_sources. Their descriptions and schemas cost roughly 365 tokens of context every time the server is loaded.

### Does the TheAIMeters MCP server require authentication?

No. We connected to TheAIMeters without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the TheAIMeters MCP server still maintained?

TheAIMeters is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the TheAIMeters MCP server?

VerifyMCP ran 13 checks on TheAIMeters, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://www.theaimeters.com/mcp
- Website: https://www.theaimeters.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-theaimeters-theaimeters/www.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-theaimeters-theaimeters/www/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-theaimeters-theaimeters/www.json
- HTML version of this page: https://verifymcp.io/servers/com-theaimeters-theaimeters/www