# Recordsure website (remote · recordsure.com)

Read-only tools for recordsure.com: contact card, documents, page search and page content.

- Trust score: 76/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `mcp.recordsure.com`: 75/100, [markdown](https://verifymcp.io/servers/com-recordsure-website/mcp.md), [page](https://verifymcp.io/servers/com-recordsure-website/mcp)
- remote · `recordsure.com`: 76/100 (this document), [markdown](https://verifymcp.io/servers/com-recordsure-website/wp-json-tcc-mcp-v1-mcp.md), [page](https://verifymcp.io/servers/com-recordsure-website/wp-json-tcc-mcp-v1-mcp)

## Channel facts

- Endpoint: `https://recordsure.com/wp-json/tcc-mcp/v1/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.4.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**: 80/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 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**: 79/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 1354 tokens (~61/item across 22 items; 18 tools + 4 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**: 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 (28% 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 18 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 20 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).
  - Supports UI / widget rendering.

## Install

### How do I install the Recordsure website MCP server?

Recordsure website is a hosted endpoint at https://recordsure.com/wp-json/tcc-mcp/v1/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-recordsure-website 'https://recordsure.com/wp-json/tcc-mcp/v1/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-recordsure-website": {
      "url": "https://recordsure.com/wp-json/tcc-mcp/v1/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-recordsure-website": {
      "type": "http",
      "url": "https://recordsure.com/wp-json/tcc-mcp/v1/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-recordsure-website]
url = "https://recordsure.com/wp-json/tcc-mcp/v1/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-recordsure-website": {
      "type": "remote",
      "url": "https://recordsure.com/wp-json/tcc-mcp/v1/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-recordsure-website --url 'https://recordsure.com/wp-json/tcc-mcp/v1/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-recordsure-website:
    url: "https://recordsure.com/wp-json/tcc-mcp/v1/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-recordsure-website": {
      "Transport": "http",
      "Url": "https://recordsure.com/wp-json/tcc-mcp/v1/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-recordsure-website -t streamable-http -u 'https://recordsure.com/wp-json/tcc-mcp/v1/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-recordsure-website": {
      "type": "http",
      "url": "https://recordsure.com/wp-json/tcc-mcp/v1/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-05 (score 76, +1)

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

### 2026-11-03 (score 75, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-02 (score 74)

First indexed and scored.

## MCP tools (18)

### `get_site_info` (~17 tokens)

Get site information

Get site metadata and MCP server capabilities.

### `list_pages` (~35 tokens)

List pages

List published WordPress pages with pagination.

Input parameters:

- `page` (integer): Integer value.
- `per_page` (integer): Integer value.

### `list_posts` (~76 tokens)

List posts, insights and case studies

List published posts, insights, or case studies, optionally filtered by taxonomy.

Input parameters:

- `page` (integer): Integer value.
- `per_page` (integer): Integer value.
- `taxonomy` (string): Optional taxonomy filter.
- `term` (string): Optional taxonomy term slug.
- `type` (string): The public post type to query.

### `list_taxonomy_terms` (~28 tokens)

List taxonomy terms

List published taxonomy terms with counts.

Input parameters:

- `taxonomy` (string): The taxonomy to enumerate.

### `search_content` (~39 tokens)

Search site content

Search public pages, posts, insights, and case studies.

Input parameters:

- `per_page` (integer): Integer value.
- `query` (string, required): Search phrase.

### `get_page_content_with_schema` (~66 tokens)

Get page content and schema

Get full page textual content and published JSON-LD schema for grounded evaluation.

Input parameters:

- `page_id` (integer): Integer value.
- `slug` (string): Page slug or path (for example: redress-and-remediation).
- `url` (string): Absolute page URL.

### `search_enriched_page_contexts` (~60 tokens)

Search enriched page contexts

Search site content and return top matching page contexts enriched with full text and JSON-LD schema.

Input parameters:

- `per_page` (integer): Integer value.
- `query` (string, required): Search phrase.
- `top_n` (integer): Integer value.

### `get_citation_links` (~57 tokens)

Get citation links

Return clean source links and markdown citation bullets for a query context.

Input parameters:

- `per_page` (integer): Integer value.
- `query` (string, required): Search phrase used to collect source links.
- `top_n` (integer): Integer value.

### `get_schema_context` (~17 tokens)

Get organisation schema context

Return the sitewide Organization schema context.

### `get_navigation` (~14 tokens)

Get site navigation

Return the primary navigation structure.

### `get_team_directory` (~34 tokens)

Get team directory

Get the published, featured team member directory (Core-managed People profiles). Read-only and published-only, like every other tool.

### `get_person_profile` (~60 tokens)

Get team member profile

Get one published team member profile and its schema.org Person JSON-LD by slug.

Input parameters:

- `slug` (string, required): The person's slug: the fragment of their url in get_team_directory, such as jane-example in /meet-the-team/#jane-example.

### `search_media_assets` (~100 tokens)

Search media assets

Search public, active Core-managed Media Assets eligible for this website and return safe delivery variants plus schema.org MediaObject JSON-LD. Private and management records are never returned.

Input parameters:

- `cursor` (string): Optional opaque cursor returned by the previous page.
- `kind` (string): Optional kind of asset to return; every kind when omitted.
- `page_size` (integer): Integer value.
- `query` (string): Optional asset title or description search phrase.

### `search_documents` (~152 tokens)

Search documents

Search the public documents (PDF files) that this website publishes and return each as a document card with its schema.org node. Filter by topic or sector (slugs), by the address of a page on this website to find the documents related to it, or search by phrase. Call get_document to open one document by its id. Only published, open documents appear, and none may be available.

Input parameters:

- `limit` (integer): Integer value.
- `page_url` (string): Optional address of a page on this website: only documents related to that page are returned.
- `query` (string): Optional search phrase.
- `sector` (string): Optional sector slug.
- `topic` (string): Optional topic slug.

Output parameters:

- `available` (boolean): False when the documents cannot be read now (reasonCode says why); true for every other answer, one with no documents included.
- `items` (array): The documents, each as a card.
- `message` (string): Why there are no documents, in plain words, when there are none.
- `reasonCode` (string): A stable code that says why the documents cannot be read, and an empty string when they can.
- `schemaVersion` (integer): The version of the shape of this answer: 1.

### `get_document` (~58 tokens)

Get document

Get one public document card, with its schema.org node, by the id that search_documents returns. A document that does not exist or is not published for this website returns the same not-found answer.

Input parameters:

- `id` (string, required): The document id.

Output parameters:

- `available` (boolean): False when the documents cannot be read now (reasonCode says why); true for every other answer, one with no documents included.
- `items` (array): The documents, each as a card.
- `message` (string): Why there are no documents, in plain words, when there are none.
- `reasonCode` (string): A stable code that says why the documents cannot be read, and an empty string when they can.
- `schemaVersion` (integer): The version of the shape of this answer: 1.

### `get_contact_options` (~116 tokens)

Get contact options

Get how a person can contact this organisation: the address of its contact page, the enquiry routes that page offers, and the email address, telephone number and office hours the site publishes. Use it when a person asks how to get in touch. A fact the site does not publish is left out, and hours and routes are stated as the site publishes them, not as a promise of availability or of a response time. Takes no arguments, accepts no personal data and sends nothing: the person completes any enquiry on the contact page themselves.

Output parameters:

- `citationGuidance` (string)
- `citationRenderInstruction` (string)
- `contactPage` (object)
- `email` (string)
- `enquiryRoutes` (array)
- `name` (string): The name of the organisation.
- `officeHours` (array)
- `schemaVersion` (integer): The version of the shape of this answer: 1.
- `sourceLinks` (array)
- `sourceLinksMarkdown` (string)
- `sources` (array)
- `telephone` (string)

### `get_document_carousel` (~183 tokens)

Show documents as cards

Use this when a person wants to see documents that search_documents or get_document returned: it shows up to three of them as a carousel of cards, each with the document's title, summary, size, number of pages and preview image, a button that opens the PDF and a link to contact the organisation. Pass the id of each document to show, taken from the id of its card, at most three. A document that is not published for this website is left out, and when none can be shown the answer is the one get_document gives for a document that is not found. Do not use it to find documents: call search_documents for that. A client that does not show cards receives the same answer as text.

Input parameters:

- `ids` (array, required): The id of each document to show, as search_documents and get_document give it: at most three.

Output parameters:

- `available` (boolean): False when the documents cannot be read now (reasonCode says why); true for every other answer, one with no documents included.
- `items` (array): The documents, each as a card.
- `message` (string): Why there are no documents, in plain words, when there are none.
- `reasonCode` (string): A stable code that says why the documents cannot be read, and an empty string when they can.
- `schemaVersion` (integer): The version of the shape of this answer: 1.

### `get_contact_card` (~154 tokens)

Show contact options as a card

Use this when a person asks how to get in touch with this organisation and would like to see it as a card: it shows the same facts as get_contact_options, which are the address of its contact page, the enquiry routes that page offers, and the email address, telephone number and office hours the site publishes, with a button that opens the contact page. A fact the site does not publish is left out, and hours and routes are stated as the site publishes them, not as a promise of availability or of a response time. Takes no arguments, accepts no personal data and sends nothing: the person completes any enquiry on the contact page themselves. A client that does not show cards receives the same answer as text.

Output parameters:

- `citationGuidance` (string)
- `citationRenderInstruction` (string)
- `contactPage` (object)
- `email` (string)
- `enquiryRoutes` (array)
- `name` (string): The name of the organisation.
- `officeHours` (array)
- `schemaVersion` (integer): The version of the shape of this answer: 1.
- `sourceLinks` (array)
- `sourceLinksMarkdown` (string)
- `sources` (array)
- `telephone` (string)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-recordsure-website/wp-json-tcc-mcp-v1-mcp#diagnostics

## Score history

- 2026-11-05: 76
- 2026-11-04: 75
- 2026-11-03: 75
- 2026-11-02: 74

## Common questions

### What is the Recordsure website MCP server?

Recordsure website is an MCP server listed in the public MCP registry as com.recordsure/website. Read-only tools for recordsure.com: contact card, documents, page search and page content. This page covers its hosted endpoint (https://recordsure.com/wp-json/tcc-mcp/v1/mcp).

### Is the Recordsure website MCP server safe to use?

Recordsure website scores 76 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 Recordsure website MCP server expose?

Recordsure website exposes 18 tools: get_site_info, list_pages, list_posts, list_taxonomy_terms, search_content, and 13 more. Their descriptions and schemas cost roughly 1,266 tokens of context every time the server is loaded.

### Does the Recordsure website MCP server require authentication?

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

### Is the Recordsure website MCP server still maintained?

Recordsure website 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 Recordsure website MCP server?

VerifyMCP ran 14 checks on Recordsure website, covering TLS certificate, Authorization, HTTPS, HSTS header and 10 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://recordsure.com/wp-json/tcc-mcp/v1/mcp
- Website: https://recordsure.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-recordsure-website/wp-json-tcc-mcp-v1-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-recordsure-website/wp-json-tcc-mcp-v1-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-recordsure-website/wp-json-tcc-mcp-v1-mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-recordsure-website/wp-json-tcc-mcp-v1-mcp