# Declared-vs-Enforced Agent Access Verification (remote · textforagents.com)

Compares declared agent access against actual enforcement per identity class, with drift watch.

- Trust score: 69/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-23

## Components

- remote · `textforagents.com`: 69/100 (this document), [markdown](https://verifymcp.io/servers/com-textforagents-declared-vs-enforced-agent-access-verification/products-declared-vs-enforced-agent-access-verification-mcp.md), [page](https://verifymcp.io/servers/com-textforagents-declared-vs-enforced-agent-access-verification/products-declared-vs-enforced-agent-access-verification-mcp)

## Channel facts

- Endpoint: `https://textforagents.com/products/declared-vs-enforced-agent-access-verification/mcp`
- Transports: `streamable-http`
- Auth: `required (not validated)`
- 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-10-23.

- **Endpoint Security**: 89/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 58/100
  - AI-judged instruction clarity (fair).
  - Tool/resource definitions use about 160 tokens (~40/item across 4 items; 4 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 10/100
  - Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 67/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
- **Tool Safety**: 75/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "drift_remove" implies "remove" and declares no destructiveHint at all, which the MCP spec reads as destructive by default.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 40/100
  - Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28.

## Install

### How do I install the Declared-vs-Enforced Agent Access Verification MCP server?

Declared-vs-Enforced Agent Access Verification is a hosted endpoint at https://textforagents.com/products/declared-vs-enforced-agent-access-verification/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-textforagents-declared-vs-enforced-agent-acc 'https://textforagents.com/products/declared-vs-enforced-agent-access-verification/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-textforagents-declared-vs-enforced-agent-acc": {
      "url": "https://textforagents.com/products/declared-vs-enforced-agent-access-verification/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-textforagents-declared-vs-enforced-agent-acc": {
      "type": "http",
      "url": "https://textforagents.com/products/declared-vs-enforced-agent-access-verification/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-textforagents-declared-vs-enforced-agent-acc]
url = "https://textforagents.com/products/declared-vs-enforced-agent-access-verification/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-textforagents-declared-vs-enforced-agent-acc": {
      "type": "remote",
      "url": "https://textforagents.com/products/declared-vs-enforced-agent-access-verification/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-textforagents-declared-vs-enforced-agent-acc --url 'https://textforagents.com/products/declared-vs-enforced-agent-access-verification/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-textforagents-declared-vs-enforced-agent-acc:
    url: "https://textforagents.com/products/declared-vs-enforced-agent-access-verification/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-textforagents-declared-vs-enforced-agent-acc": {
      "Transport": "http",
      "Url": "https://textforagents.com/products/declared-vs-enforced-agent-access-verification/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-textforagents-declared-vs-enforced-agent-acc -t streamable-http -u 'https://textforagents.com/products/declared-vs-enforced-agent-access-verification/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-textforagents-declared-vs-enforced-agent-acc": {
      "type": "http",
      "url": "https://textforagents.com/products/declared-vs-enforced-agent-access-verification/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-10-23 (score 69, −1)

- [security] Tool “drift_run” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: 121 → 160
- [functional] Destructive annotations: pass → 0
- [functional] Server version: 1.0.1 → 1.0.3
- [functional] New tool “drift_remove”

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

- [functional] Server version: 1.0.0 → 1.0.1

### 2026-10-21 (score 69, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-20 (score 69)

First indexed and scored.

## MCP tools (4)

### `access_probe` (~77 tokens)

Pre-flight declared-vs-enforced probe of one target path (one-time grant; the $0.01 x402 rail is the HTTP /probe endpoint).

Input parameters:

- `agent_token` (string)
- `base_url` (string, required)
- `fixture` (string)
- `path` (string)
- `signed` (boolean)

### `drift_targets` (~15 tokens)

List your enrolled drift-watch targets.

### `drift_run` (~40 tokens)

Re-probe one enrolled target now and record two-sided drift (manual runs metered: 1/min/target).

Input parameters:

- `target_id` (string, required)

### `drift_remove` (~28 tokens)

Remove one enrolled drift-watch target (records no drift event).

Input parameters:

- `target_id` (string, required)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-textforagents-declared-vs-enforced-agent-access-verification/products-declared-vs-enforced-agent-access-verification-mcp#diagnostics

## Score history

- 2026-10-23: 69
- 2026-10-22: 70
- 2026-10-21: 69
- 2026-10-20: 69

## Common questions

### What is the Declared-vs-Enforced Agent Access Verification MCP server?

Declared-vs-Enforced Agent Access Verification is an MCP server listed in the public MCP registry as com.textforagents/declared-vs-enforced-agent-access-verific…. Compares declared agent access against actual enforcement per identity class, with drift watch. This page covers its hosted endpoint (https://textforagents.com/products/declared-vs-enforced-agent-access-verification/mcp).

### Is the Declared-vs-Enforced Agent Access Verification MCP server safe to use?

Declared-vs-Enforced Agent Access Verification scores 69 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 Declared-vs-Enforced Agent Access Verification MCP server expose?

Declared-vs-Enforced Agent Access Verification exposes 4 tools: access_probe, drift_targets, drift_run, drift_remove. Their descriptions and schemas cost roughly 160 tokens of context every time the server is loaded.

### Does the Declared-vs-Enforced Agent Access Verification MCP server require authentication?

Yes. Declared-vs-Enforced Agent Access Verification asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

### Is the Declared-vs-Enforced Agent Access Verification MCP server still maintained?

Declared-vs-Enforced Agent Access Verification is still listed as active in the MCP registry. We last reached this channel on 23 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://textforagents.com/products/declared-vs-enforced-agent-access-verification/mcp
- Website: https://textforagents.com/products/declared-vs-enforced-agent-access-verification/
- Changelog RSS feed: https://verifymcp.io/servers/com-textforagents-declared-vs-enforced-agent-access-verification/products-declared-vs-enforced-agent-access-verification-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-textforagents-declared-vs-enforced-agent-access-verification/products-declared-vs-enforced-agent-access-verification-mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-textforagents-declared-vs-enforced-agent-access-verification/products-declared-vs-enforced-agent-access-verification-mcp