# Let Agents In (remote · letagentsin.com)

Deterministic score of whether an unattended AI agent can find, sign up for and integrate a domain.

- Trust score: 63/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-20

## Components

- remote · `letagentsin.com`: 63/100 (this document), [markdown](https://verifymcp.io/servers/com-letagentsin-scanner/letagentsin.md), [page](https://verifymcp.io/servers/com-letagentsin-scanner/letagentsin)

## Channel facts

- Endpoint: `https://letagentsin.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-08-20.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - 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**: 67/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 549 tokens (~274/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 7/100
  - Stability observed for 2 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.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http com-letagentsin-scanner https://letagentsin.com/mcp
```

### Codex

```toml
[mcp_servers.com-letagentsin-scanner]
url = "https://letagentsin.com/mcp"
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add com-letagentsin-scanner --url https://letagentsin.com/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-letagentsin-scanner:
    url: "https://letagentsin.com/mcp"
```

### Other

```json
{
  "mcpServers": {
    "com-letagentsin-scanner": {
      "type": "http",
      "url": "https://letagentsin.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-08-20 (score 63, +1)

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

### 2026-08-19 (score 62, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-08-18 (score 62)

First indexed and scored.

## MCP tools (2)

### `scan_domain` (~126 tokens)

Scan a domain for agent readiness

Scores a domain across 5 funnel stages using 16 deterministic HTTP checks. 18 points exist on paper; the score is out of the points that both applied to the domain and could be evaluated. Returns a per-check breakdown with the reason for each result and a permanent link.

Input parameters:

- `domain` (string, required): Bare domain, for example example.com
- `format` (string): summary is the readable breakdown. agent returns markdown instructions you can act on directly, each task carrying the measurement behind it. sarif returns SARIF 2.1.0 for a code-scanning pipeline.

### `find_providers` (~351 tokens)

Find providers an unattended agent can actually finish with

Describe the problem in your own words, for example "let users upload images" or "send transactional email". Returns the vendors we have measured in that category, split by whether an unattended run clears every barrier we test, stops at one, or was never measurable, each with the date and a link to the evidence. This is not a recommendation: it does not know whether a vendor suits your job, only where an agent stops. Routing a sentence to a category is by far the weakest thing here, and the numbers below are the ones to plan around. Measured on 40 questions written by an agent with no access to this repository and no sight of the category list, labelled before the first run, and built to be hard: fourteen of them ask about the caller own code in commercial words (a billing module, a payments table, a notifications worker), and six ask for something real that a catalogue this size does not hold. It got 29 of the 40 right, said nothing on 8 it should have answered, sent 0 to the wrong category and answered 3 that it should have refused. Put another way: it gave an answer to 14 of the 40, and 3 of those answers were wrong, while refusing 18 of the 21 it should have refused. It is deliberately quiet. One vocabulary word inside a long question decides nothing, and a question shaped like a request for code rather than for a vendor is refused outright. Silence means we could not read the question, not that the category is empty. The tool reads English. Name the category yourself when you know it.

Input parameters:

- `job` (string, required): The problem to solve, in your own words.

## Diagnostics

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

## Score history

- 2026-08-20: 63
- 2026-08-19: 62
- 2026-08-18: 62

## Links

- Remote endpoint: https://letagentsin.com/mcp
- Website: https://letagentsin.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-letagentsin-scanner/letagentsin.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-letagentsin-scanner/letagentsin.json
- HTML version of this page: https://verifymcp.io/servers/com-letagentsin-scanner/letagentsin