Skip to content

MCP Security Check

api.assign2me.com/mcp

F

54 of 100

Checked November 22, 20265 failed · 16 passed · 1 could not check

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

Failed 5

High

Implicit flow advertised

MCPS-AUTH-009

Why it mattersThe implicit flow puts the access token in the browser's address. RFC 9700 advises against it, and OAuth 2.1 drops it.

How to fixRemove token from response_types_supported and use the code flow with PKCE.

Request
GET https://iam.trogon.pl/.well-known/oauth-authorization-server/realms/assign2me
What we saw
response_types_supported: ["code","none","id_token","token","id_token token","code id_token","code token","code id_token token"]

Seen in the server's answer

SpecRFC 9700, Section 2.1.2 (Implicit Grant)

High

Password grant advertised

MCPS-AUTH-010

Why it mattersThe password grant hands the person's password to the client. RFC 9700 says it must not be used.

How to fixRemove password from grant_types_supported.

Request
GET https://iam.trogon.pl/.well-known/oauth-authorization-server/realms/assign2me
What we saw
grant_types_supported: ["authorization_code","client_credentials","implicit","password","refresh_token","urn:ietf:params:oauth:grant-type:device_code","urn:ietf:params:oauth:grant-type:jwt-bearer","urn:ietf:params:oauth:grant-type:token-exchange","urn:ietf:params:oauth:grant-type:uma-ticket","urn:o…

Seen in the server's answer

SpecRFC 9700, Section 2.4 (Resource Owner Password Credentials Grant MUST NOT be used)

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://api.assign2me.com/mcp (initialize)
Answer
401
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://api.assign2me.com/mcp (initialize)
Answer
401
What we saw
no X-Content-Type-Options: nosniff

Seen in the server's answer

SpecFetch Standard, X-Content-Type-Options

Low

PKCE plain method offered

MCPS-AUTH-008

Why it mattersWith plain, the challenge equals the secret, so anyone who sees the request sees the secret.

How to fixOffer S256 only.

Request
GET https://iam.trogon.pl/.well-known/oauth-authorization-server/realms/assign2me
What we saw
code_challenge_methods_supported: ["plain","S256"]

Seen in the server's answer

SpecRFC 9700, Section 2.1.1 (PKCE: S256)

Notes, not scored 2

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://api.assign2me.com/mcp (initialize)
Answer
401
What we saw
no Referrer-Policy

Seen in the server's answer

SpecReferrer Policy (W3C)

Note

Dynamic registration only

MCPS-AUTH-014

Why it mattersA note, not scored: MCP 2026-07-28 deprecates dynamic client registration in favour of client ID metadata documents.

How to fixAdd client ID metadata document support and keep dynamic registration for older clients.

Request
GET https://iam.trogon.pl/.well-known/oauth-authorization-server/realms/assign2me
What we saw
registration_endpoint only

Seen in the server's answer

SpecMCP 2026-07-28, Deprecated Features: Dynamic Client Registration (PR #2858)

Could not check 1

  • Answers a request from a foreign websiteMCPS-ORIGIN-001
Passed 16
  • Accepts a made-up tokenMCPS-AUTH-001
  • Served over plain HTTPMCPS-TLS-001
  • Certificate not trusted or not for this hostMCPS-TLS-002
  • Sign-in metadata names no authorization serverMCPS-AUTH-004
  • Authorization server metadata names another issuerMCPS-AUTH-006
  • PKCE with S256 not advertisedMCPS-AUTH-007
  • Sign-in endpoint over plain HTTPMCPS-AUTH-015
  • Any website can read answers sent with the person's cookiesMCPS-CORS-001
  • Certificate expires within 14 daysMCPS-TLS-003
  • 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
  • Issuer in the authorization response not advertisedMCPS-AUTH-011
  • Refresh tokens without an advertised revocation endpointMCPS-AUTH-012
  • Any website may read the answersMCPS-CORS-002
Does not apply 8
  • 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
  • Hidden instruction in a prompt or resourceMCPS-TOOL-003
  • States an SDK version with known advisoriesMCPS-SDK-001
  • A destructive tool says it is safeMCPS-TOOL-004
  • A destructive tool says it only readsMCPS-TOOL-005
  • Uses deprecated loggingMCPS-PROTO-001

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 22, 2026.

In the INITE Atlas

Answered on 100% of days in the last monthIts 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 F
[![MCP security F](https://inite.ai/api/checks/mcp/badge/api.assign2me.com/mcp.svg)](https://inite.ai/en/mcp-check/api.assign2me.com/mcp)

As JSON