Skip to content

MCP Security Check

modelsalt.com/mcp

A

94 of 100

Checked November 22, 20263 failed · 10 passed · 0 could not check

A passive check: only what any client sees. No tool was called and no client was registered.

Failed 3

Low

No Strict-Transport-Security header

MCPS-HDR-001

Why it mattersWithout it, an attacker can keep a browser on plain HTTP on any later visit. HSTS makes the browser use HTTPS only.

How to fixSend Strict-Transport-Security: max-age=31536000 on every HTTPS response.

return new Response(body, { headers: { 'Strict-Transport-Security': 'max-age=31536000; includeSubDomains' } })
app.use((req, res, next) => { res.setHeader('Strict-Transport-Security', 'max-age=31536000; includeSubDomains'); next() })
Request
POST https://modelsalt.com/mcp (initialize)
Answer
200
What we saw
no Strict-Transport-Security

Seen in the server's answer

SpecRFC 6797 (HTTP Strict Transport Security)

Low

No X-Content-Type-Options: nosniff

MCPS-HDR-002

Why it mattersA browser may guess a response's type and render JSON or text as HTML or script.

How to fixSend X-Content-Type-Options: nosniff on every response.

res.setHeader('X-Content-Type-Options', 'nosniff')
Request
POST https://modelsalt.com/mcp (initialize)
Answer
200
What we saw
no X-Content-Type-Options: nosniff

Seen in the server's answer

SpecFetch Standard, X-Content-Type-Options

Low

Answers a request from a foreign website

MCPS-ORIGIN-001

Why it mattersThe MCP spec requires a 403 for an Origin the server does not expect. On a public server this keeps other websites' pages from calling it through a visitor's browser; on a server running on someone's own machine, it is what stops a web page from reaching it (DNS rebinding, behind CVE-2025-66414 and CVE-2025-66416).

How to fixWhen an Origin header is present and not on your list, answer 403; requests without one, from programs, keep working. In the official SDKs, turn on DNS rebinding protection and list the allowed origins and hosts.

new StreamableHTTPServerTransport({ enableDnsRebindingProtection: true, allowedOrigins: ['https://claude.ai'], allowedHosts: ['mcp.example.com'] })
const origin = request.headers.get('Origin'); if (origin && !ALLOWED.has(origin)) return new Response(null, { status: 403 })
Request
POST https://modelsalt.com/mcp (initialize, Origin: https://probe.invalid)
Answer
200
What we saw
{"jsonrpc":"2.0","id":1,"result":{"protocolVersion":"2025-06-18","capabilities":{"tools":{}},"serverInfo":{"name":"model-salt-openai-hosted","version":"1.0.0-numbers"},"instructions":"Model Salt: for a creative or open-ended request (a picture, an SVG, a story, a poem, a design, a name, a plan), fi…

Seen in the server's answer

SpecMCP 2026-07-28, Transports, Streamable HTTP: Security & Endpoint, item 1CVE-2025-66414 (TypeScript SDK), CVE-2025-66416 (Python SDK): DNS rebinding protection off by default

Notes, not scored 2

Note

Any website may read the answers

MCPS-CORS-002

Why it mattersA note, not scored: Access-Control-Allow-Origin: * is normal for an open, read-only server, and wrong for one that holds private data.

How to fixIf the server answers with private data, list the origins that may read it instead of *.

Request
POST https://modelsalt.com/mcp (initialize, Origin: https://probe.invalid)
Answer
200
What we saw
Access-Control-Allow-Origin: *

Seen in the server's answer

SpecFetch Standard, Access-Control-Allow-Origin

Note

No Referrer-Policy header

MCPS-HDR-003

Why it mattersA note, not scored: it matters when the endpoint also serves pages a browser opens.

How to fixSend Referrer-Policy: no-referrer or strict-origin-when-cross-origin.

Request
POST https://modelsalt.com/mcp (initialize)
Answer
200
What we saw
no Referrer-Policy

Seen in the server's answer

SpecReferrer Policy (W3C)

Passed 10
  • Served over plain HTTPMCPS-TLS-001
  • Certificate not trusted or not for this hostMCPS-TLS-002
  • Tools that change things answer anyoneMCPS-AUTH-016
  • Hidden instruction in a tool's textMCPS-TOOL-001
  • Invisible characters in a tool's textMCPS-TOOL-002
  • Any website can read answers sent with the person's cookiesMCPS-CORS-001
  • Certificate expires within 14 daysMCPS-TLS-003
  • A destructive tool says it is safeMCPS-TOOL-004
  • A destructive tool says it only readsMCPS-TOOL-005
  • Uses deprecated loggingMCPS-PROTO-001
Does not apply 17
  • Accepts a made-up tokenMCPS-AUTH-001
  • Sign-in metadata names no authorization serverMCPS-AUTH-004
  • Authorization server metadata names another issuerMCPS-AUTH-006
  • PKCE with S256 not advertisedMCPS-AUTH-007
  • Implicit flow advertisedMCPS-AUTH-009
  • Password grant advertisedMCPS-AUTH-010
  • Sign-in endpoint over plain HTTPMCPS-AUTH-015
  • Hidden instruction in a prompt or resourceMCPS-TOOL-003
  • States an SDK version with known advisoriesMCPS-SDK-001
  • Wrong status for an invalid tokenMCPS-AUTH-002
  • Clients cannot find how to sign inMCPS-AUTH-003
  • Sign-in metadata names another resourceMCPS-AUTH-005
  • Clients cannot register themselvesMCPS-AUTH-013
  • PKCE plain method offeredMCPS-AUTH-008
  • Issuer in the authorization response not advertisedMCPS-AUTH-011
  • Refresh tokens without an advertised revocation endpointMCPS-AUTH-012
  • Dynamic registration onlyMCPS-AUTH-014

Tool changes

A server can change what a tool does after people approved it. We keep a fingerprint of every tool from the first check.

No tool changes since November 21, 2026.

In the INITE Atlas

Answered on 100% of days in the last monthTool definitions: grade AIts Atlas page
Is this your server? Prove it to run the sign-in tests a passive check cannot and, if you own its Atlas card, have it checked every day with an alert when anything changes.
This server is mine

Badge for your README

MCP security A
[![MCP security A](https://inite.ai/api/checks/mcp/badge/modelsalt.com/mcp.svg)](https://inite.ai/en/mcp-check/modelsalt.com/mcp)

As JSON