com.eformogi/records-vault
REMOTE · EFORMOGI.COM · SCANNED OCT 4
Consent-scoped vault access and free verification of family-issued learning records.
Available components
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 Security89
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Fail
- 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 Usability81
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 571 tokens (~63/item across 9 items; 9 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management7
- Stability observed for 2 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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities40
- Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28. See how to fix → Fail
How do I install the com.eformogi/records-vault MCP server?
com.eformogi/records-vault is a hosted endpoint at https://eformogi.com/api/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 · eformogi.com
claude mcp add --transport http com-eformogi-records-vault 'https://eformogi.com/api/mcp'
{
"mcpServers": {
"com-eformogi-records-vault": {
"url": "https://eformogi.com/api/mcp"
}
}
} {
"servers": {
"com-eformogi-records-vault": {
"type": "http",
"url": "https://eformogi.com/api/mcp"
}
}
} [mcp_servers.com-eformogi-records-vault] url = "https://eformogi.com/api/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-eformogi-records-vault": {
"type": "remote",
"url": "https://eformogi.com/api/mcp",
"enabled": true
}
}
} openclaw mcp add com-eformogi-records-vault --url 'https://eformogi.com/api/mcp' --transport streamable-http
mcp_servers:
com-eformogi-records-vault:
url: "https://eformogi.com/api/mcp" {
"McpServers": {
"com-eformogi-records-vault": {
"Transport": "http",
"Url": "https://eformogi.com/api/mcp"
}
}
} assistant mcp add com-eformogi-records-vault -t streamable-http -u 'https://eformogi.com/api/mcp'
{
"mcpServers": {
"com-eformogi-records-vault": {
"type": "http",
"url": "https://eformogi.com/api/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 4 Oct 26 +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.
- 3 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 2 Oct 26 +40
- Transport: unverified → pass ▲ security
- Injection markers: unverified → pass ▲ security
- First check of Judged manipulation: pass security
- Authorization: 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. security
- MCP protocol: unverified → fail ▼ functional
- Tool coverage: unverified → 100 ▲ functional
- First check of Schema quality: fail functional
- First check of Schema quality: excellent functional
- First check of Destructive annotations: pass functional
- First check of Schema quality: pass functional
- First check of Tool coverage: 100 functional
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
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 6 Oct 2026 · Probed https://eformogi.com/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=eformogi.com | CN=YR2,O=Let's Encrypt,C=US | 25 Aug 2026 | 23 Nov 2026 | RSA 2048 | SHA256-RSA | 6f6d9ec5fc4db86219bc428c26fe2368e33 |
| SANs: eformogi.com | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of eformogi.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| eformogi.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Challenged, unverified
The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.
| Result | Challenged, unverified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| content-security-policy | default-src 'self'; script-src 'self' 'unsafe-inline' https://www.googletagmanager.com; style-src 'self' 'unsafe-inline' https://fonts.googleapis.com; connect-src 'self' https://*.supabase.co wss://*.supabase.co https://generativelanguage.googleapis.com https://api.openai.com https://js.stripe.com https://*.google-analytics.com https://*.analytics.google.com https://*.googletagmanager.com https://www.google.com https://*.ingest.sentry.io https://*.ingest.us.sentry.io; img-src 'self' data: blob: https://*.supabase.co https://*.google-analytics.com https://*.googletagmanager.com https://api.qrserver.com; font-src 'self' https://fonts.gstatic.com; frame-src https://js.stripe.com; worker-src 'self' blob:; manifest-src 'self'; base-uri 'self'; form-action 'self' |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(self), geolocation=() |
Protected resource metadata
| Retrieved | No |
|---|---|
| Problem | no_resource_metadata |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://eformogi.com/api/mcp | Verified | 200 | |
| http (plaintext) | http://eformogi.com/api/mcp | HTTPS enforced | 308 | https://eformogi.com/api/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 →
check_policy ~29
Check what data categories the agent is allowed to access and their policy level (auto/ask/never).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
create_consent ~65
Create a consent grant to share specific categories with an organization. Categories under "ask" policy will require user approval.
| Name | Type | Req | Description |
|---|---|---|---|
| categories | array | yes | Categories to share |
| org_name | string | yes | Organization name |
| purpose | string | yes | Why the data is being shared |
No output schema declared.
No examples provided.
how_eformogi_works ~39
What Eformogi is and what it costs: the thesis sentence and the pricing paragraph, verbatim, plus the key public pages.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_consents ~38
List the user's active consent receipts — who they've shared data with and what categories.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Max results (default 20) |
No output schema declared.
No examples provided.
log_action ~56
Log an action the agent performed on behalf of the user. All MCP calls are auto-logged, but agents can add explicit action descriptions.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | What the agent did |
| details | object | – | Additional context |
No output schema declared.
No examples provided.
read_profile ~59
Read the user's vault data for specified categories. Respects the agent policy — auto categories return data, ask categories return pending, never categories are denied.
| Name | Type | Req | Description |
|---|---|---|---|
| categories | array | yes | Data categories to read (e.g. basic_info, medical, education) |
No output schema declared.
No examples provided.
read_spec ~76
Read the open Eformogi record standard published at /spec. With no chapter, lists every published chapter. With a chapter slug, returns that chapter's markdown text.
| Name | Type | Req | Description |
|---|---|---|---|
| chapter | string | – | A chapter slug from the list (e.g. "record-model", "verification", "issuing"). Omit to list every chapter. |
No output schema declared.
No examples provided.
search_orgs ~32
Search for organizations the user can share data with.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | Search term (name or type) |
No output schema declared.
No examples provided.
verify_record ~114
Verify an Eformogi receipt id with no login and no API key: the same check the public /verify page performs. Returns the kind, the title or course fields, the issued date, and the signers' names and identity levels, worded exactly as the page words them. Never an email, a user id, or a person id.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | An Eformogi receipt id: tr_, cr_, ws_, att_, wn_, wl_, or kb_ followed by 12 hex characters. |
No output schema declared.
No examples provided.
What is the com.eformogi/records-vault MCP server?
com.eformogi/records-vault is an MCP server listed in the public MCP registry as com.eformogi/records-vault. Consent-scoped vault access and free verification of family-issued learning records. This page covers its hosted endpoint (https://eformogi.com/api/mcp).
Is the com.eformogi/records-vault MCP server safe to use?
com.eformogi/records-vault scores 77 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 com.eformogi/records-vault MCP server expose?
com.eformogi/records-vault exposes 9 tools: read_profile, list_consents, create_consent, check_policy, log_action, and 4 more. Their descriptions and schemas cost roughly 508 tokens of context every time the server is loaded.
Does the com.eformogi/records-vault MCP server require authentication?
Yes. com.eformogi/records-vault 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 com.eformogi/records-vault MCP server still maintained?
com.eformogi/records-vault is still listed as active in the MCP registry. We last reached this channel on 4 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.