Recordsure website
REMOTE · RECORDSURE.COM · 2 COMPONENTS
Read-only tools for recordsure.com: contact card, documents, page search and page content.
Available components
Last scanned (10 hours ago)
Scores higher than 66% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Search and Retrieval
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. How we score → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability79
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 1354 tokens (~61/item across 22 items; 18 tools + 4 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management10
- Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (28% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 18 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 20 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
- Supports UI / widget rendering.Pass
Checks we ran (14)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
- Capabilities
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 5 Nov 26 +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.
- 3 Nov 26 +1
- Stability: unverified → 0.03 ▲ functional
- 2 Nov 26 74
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://recordsure.com/wp-json/tcc-mcp/v1/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_256_GCM_SHA384 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=recordsure.com | CN=GeoTrust TLS RSA CA G1,OU=www.digicert.com,O=DigiCert Inc,C=US | 18 Oct 2026 | 18 Apr 2027 | RSA 2048 | SHA256-RSA | 234dd2ce7af1399cd882d1512375f1a |
| SANs: recordsure.com | ||||||
| CN=GeoTrust TLS RSA CA G1,OU=www.digicert.com,O=DigiCert Inc,C=US (CA) | CN=DigiCert Global Root G2,OU=www.digicert.com,O=DigiCert Inc,C=US | 2 Nov 2017 | 2 Nov 2027 | RSA 2048 | SHA256-RSA | d07782a133fc6f9a57296e131ffd179 |
| CN=DigiCert Global Root G2,OU=www.digicert.com,O=DigiCert Inc,C=US (CA) | CN=DigiCert Global Root G2,OU=www.digicert.com,O=DigiCert Inc,C=US | 1 Aug 2013 | 15 Jan 2038 | RSA 2048 | SHA256-RSA | 33af1e6a711a9a0bb2864b11d09fae5 |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of recordsure.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| recordsure.com. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains; preload |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | geolocation=(), microphone=(), camera=(), payment=(), usb=(), midi=(), sync-xhr=(), magnetometer=(), gyroscope=(), fullscreen=(self), tools=(self) |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://recordsure.com/wp-json/tcc-mcp/v1/mcp | Verified | 200 | |
| http (plaintext) | http://recordsure.com/wp-json/tcc-mcp/v1/mcp | HTTPS enforced | 307 | https://recordsure.com/wp-json/tcc-mcp/v1/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_citation_links Get citation links ~57
Return clean source links and markdown citation bullets for a query context.
| Name | Type | Req | Description |
|---|---|---|---|
| per_page | integer | – | Integer value. |
| query | string | yes | Search phrase used to collect source links. |
| top_n | integer | – | Integer value. |
No output schema declared.
No examples provided.
get_contact_card Show contact options as a card ~154
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.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| citationGuidance | string | – | – |
| citationRenderInstruction | string | – | – |
| contactPage | object | – | – |
| string | – | – | |
| enquiryRoutes | array | – | – |
| name | string | – | The name of the organisation. |
| officeHours | array | – | – |
| schemaVersion | integer | yes | The version of the shape of this answer: 1. |
| sourceLinks | array | – | – |
| sourceLinksMarkdown | string | – | – |
| sources | array | – | – |
| telephone | string | – | – |
No examples provided.
get_contact_options Get contact options ~116
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.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| citationGuidance | string | – | – |
| citationRenderInstruction | string | – | – |
| contactPage | object | – | – |
| string | – | – | |
| enquiryRoutes | array | – | – |
| name | string | – | The name of the organisation. |
| officeHours | array | – | – |
| schemaVersion | integer | yes | The version of the shape of this answer: 1. |
| sourceLinks | array | – | – |
| sourceLinksMarkdown | string | – | – |
| sources | array | – | – |
| telephone | string | – | – |
No examples provided.
get_document Get document ~58
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.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The document id. |
| Name | Type | Req | Description |
|---|---|---|---|
| available | boolean | yes | False when the documents cannot be read now (reasonCode says why); true for every other answer, one with no documents included. |
| items | array | yes | The documents, each as a card. |
| message | string | – | Why there are no documents, in plain words, when there are none. |
| reasonCode | string | yes | A stable code that says why the documents cannot be read, and an empty string when they can. |
| schemaVersion | integer | yes | The version of the shape of this answer: 1. |
No examples provided.
get_document_carousel Show documents as cards ~183
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.
| Name | Type | Req | Description |
|---|---|---|---|
| ids | array | yes | The id of each document to show, as search_documents and get_document give it: at most three. |
| Name | Type | Req | Description |
|---|---|---|---|
| available | boolean | yes | False when the documents cannot be read now (reasonCode says why); true for every other answer, one with no documents included. |
| items | array | yes | The documents, each as a card. |
| message | string | – | Why there are no documents, in plain words, when there are none. |
| reasonCode | string | yes | A stable code that says why the documents cannot be read, and an empty string when they can. |
| schemaVersion | integer | yes | The version of the shape of this answer: 1. |
No examples provided.
get_navigation Get site navigation ~14
Return the primary navigation structure.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_page_content_with_schema Get page content and schema ~66
Get full page textual content and published JSON-LD schema for grounded evaluation.
| Name | Type | Req | Description |
|---|---|---|---|
| page_id | integer | – | Integer value. |
| slug | string | – | Page slug or path (for example: redress-and-remediation). |
| url | string | – | Absolute page URL. |
No output schema declared.
No examples provided.
get_person_profile Get team member profile ~60
Get one published team member profile and its schema.org Person JSON-LD by slug.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | The person's slug: the fragment of their url in get_team_directory, such as jane-example in /meet-the-team/#jane-example. |
No output schema declared.
No examples provided.
get_schema_context Get organisation schema context ~17
Return the sitewide Organization schema context.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_site_info Get site information ~17
Get site metadata and MCP server capabilities.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_team_directory Get team directory ~34
Get the published, featured team member directory (Core-managed People profiles). Read-only and published-only, like every other tool.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_pages List pages ~35
List published WordPress pages with pagination.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | Integer value. |
| per_page | integer | – | Integer value. |
No output schema declared.
No examples provided.
list_posts List posts, insights and case studies ~76
List published posts, insights, or case studies, optionally filtered by taxonomy.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
list_taxonomy_terms List taxonomy terms ~28
List published taxonomy terms with counts.
| Name | Type | Req | Description |
|---|---|---|---|
| taxonomy | string | – | The taxonomy to enumerate. |
No output schema declared.
No examples provided.
search_content Search site content ~39
Search public pages, posts, insights, and case studies.
| Name | Type | Req | Description |
|---|---|---|---|
| per_page | integer | – | Integer value. |
| query | string | yes | Search phrase. |
No output schema declared.
No examples provided.
search_documents Search documents ~152
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| available | boolean | yes | False when the documents cannot be read now (reasonCode says why); true for every other answer, one with no documents included. |
| items | array | yes | The documents, each as a card. |
| message | string | – | Why there are no documents, in plain words, when there are none. |
| reasonCode | string | yes | A stable code that says why the documents cannot be read, and an empty string when they can. |
| schemaVersion | integer | yes | The version of the shape of this answer: 1. |
No examples provided.
search_enriched_page_contexts Search enriched page contexts ~60
Search site content and return top matching page contexts enriched with full text and JSON-LD schema.
| Name | Type | Req | Description |
|---|---|---|---|
| per_page | integer | – | Integer value. |
| query | string | yes | Search phrase. |
| top_n | integer | – | Integer value. |
No output schema declared.
No examples provided.
search_media_assets Search media assets ~100
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
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.
remote · recordsure.com
claude mcp add --transport http com-recordsure-website 'https://recordsure.com/wp-json/tcc-mcp/v1/mcp'
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.