Clay Seal MCP server

by clayseal·io.github.clayseal/clayseal·v0.6.2

Authorizes MCP tool calls against a session policy, not one call at a time.

B83/100grade B

What users say

No reviews yet

Safety scan

B83/100

Adoption

New

1 stars

Reviews

Nobody has reviewed Clay Seal yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

No tool declarations could be read from the package source. They show once the server is installed.

scanner v0.1.9 · 2026-09-20 · same rubric, same numbers if you re-run it

1 medium

Code scan204 source files scanned20/25
–Live reliabilityno gateway calls yet and no remote to proben/a
–Tool poisoningtools not inspected (local package is not executed); not countedn/a
Auth qualitylocal package, no credentials required12/15
Maintenancelast push 11 days ago15/15
Maintainer identityregistry namespace matches repository owner7/10

mediumeval / new Function usedexec.eval

clayseal-0.6.2/clayseal/capabilities/monitor/scoring/transformer.py: …) self.model = model.to(device).eval() self.vocab = vocab sel…

Overall 83/100. Components that don't apply are left out of the denominator. Any critical finding is an F.Rubric Appeal a finding JSON

claude mcp add clayseal -- uvx clayseal

Is Clay Seal MCP server safe?: Mostly: it is graded B (83/100). Read the Clay Seal safety report
How do I install Clay Seal?: It runs on your machine. Copy the Claude Code, Claude Desktop or Cursor config from the install section.
Does Clay Seal need an API key?: Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is Clay Seal maintained?: The last commit was 12 days ago (2026-09-08). The latest release is v0.6.2.