Is io.github.SPAZIO-GENESI/attest-mcp-remote safe to use?

io.github.SPAZIO-GENESI/attest-mcp-remote has no known CVEs as of the latest MCPpedia security scan. It does not require authentication, so any local process can connect — keep this in mind in shared environments. Licensed under MIT.

How do I install io.github.SPAZIO-GENESI/attest-mcp-remote?

io.github.SPAZIO-GENESI/attest-mcp-remote supports copy-paste install configs on its MCPpedia page for Claude Desktop, Cursor, and Claude Code. Scroll to the Quick Install section and select your client.

What can io.github.SPAZIO-GENESI/attest-mcp-remote do?

io.github.SPAZIO-GENESI/attest-mcp-remote provides 5 tools: Status, Tools, Develop, Security, License. See the full tools list on the server page for descriptions and parameters.

What AI clients work with io.github.SPAZIO-GENESI/attest-mcp-remote?

io.github.SPAZIO-GENESI/attest-mcp-remote is compatible with claude-desktop, cursor, claude-code. It uses stdio transport.

Is io.github.SPAZIO-GENESI/attest-mcp-remote actively maintained?

io.github.SPAZIO-GENESI/attest-mcp-remote is actively maintained — last commit was 3 days ago.

io.github.SPAZIO-GENESI/attest-mcp-remote

npm

Zero-install remote MCP server for proof-of-existence file attestation.

15.5M/wk 5 tools GitHub npm

No known CVEs

MIT license

Actively maintained

Last commit 3d ago

Works with most clients

Transport:

5 tools · ~155 tok

Grade A · 0.1% of 200K ctx

MCPpedia last refreshed this data 19h ago

Edit this pageView history

io.github.SPAZIO-GENESI/attest-mcp-remote is an MCP server that zero-install remote MCP server for proof-of-existence file attestation. Its tool list has not been published yet, requires no API key, and scores 88/100 on MCPpedia's security, maintenance and efficiency rubric.

Other

Step 1

Install in your client

Config is the same across clients — only the file and path differ.

Supported in Claude Desktopstdio · Node 18+

Paste into ~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "io-github-spazio-genesi-attest-mcp-remote": {
      "args": [
        "-y",
        "npm"
      ],
      "command": "npx"
    }
  }
}

Are you the author?

Add this badge to your README to show your security score and help users find safe servers.

Embed in your READMEAbout badges →

[![MCPpedia Score](https://mcppedia.org/api/badge/io-github-spazio-genesi-attest-mcp-remote)](https://mcppedia.org/s/io-github-spazio-genesi-attest-mcp-remote)

Read me

What io.github.SPAZIO-GENESI/attest-mcp-remote does

Listed on the official MCP Registry as io.github.SPAZIO-GENESI/attest-mcp-remote.

Test This Server

Run this in your terminal to verify the server starts. Then let us know if it worked — your result helps other developers.

npx -y 'npm' 2>&1 | head -1 && echo "✓ Server started successfully"

After testing, let us know if it worked:

Loading README…

Scored, not listed

Why this score

Five weighted categories — click any category to see the underlying evidence.

Score breakdown

88/100across 5 weighted dimensions

How we score →

0255075100

−12

Security

Maintenance

Efficiency

Documentation

Compatibility

Categoriesclick a row to see evidence

Security

OSV.dev

8 fixed

CVE-2022-29244high · fixedCVSS 7.5

Packing does not respect root-level ignore files in workspaces

### Impact `npm pack` ignores root-level `.gitignore` & `.npmignore` file exclusion directives when run in a workspace or with a workspace flag (ie. `--workspaces`, `--workspace=<name>`). Anyone who has run `npm pack` or `npm publish` with workspaces, as of [v7.9.0](https://github.com/npm/cli/releases/tag/v7.9.0) & [v7.13.0](https://github.com/npm/cli/releases/tag/v7.13.0) respectively, may be affected and have published files into the npm registry they did not intend to include. ### Patch - Up

Affected: >= 7.9.0Fixed in 8.11.0source →

CVE-2018-7408high · fixedCVSS 7.8

Incorrect Permission Assignment for Critical Resource in NPM

An issue was discovered in an npm 5.7.0 2018-02-21 pre-release (marked as "next: 5.7.0" and therefore automatically installed by an "npm upgrade -g npm" command, and also announced in the vendor's blog without mention of pre-release status). It might allow local users to bypass intended filesystem access restrictions because ownerships of /etc and /usr directories are being changed unexpectedly, related to a "correctMkdir" issue.

Affected: >= 0Fixed in 5.7.1source →

CVE-2013-4116low · fixed

Local Privilege Escalation in npm

Affected versions of `npm` use predictable temporary file names during archive unpacking. If an attacker can create a symbolic link at the location of one of these temporary file names, the attacker can arbitrarily write to any file that the user which owns the `npm` process has permission to write to, potentially resulting in local privilege escalation. ## Recommendation Update to version 1.3.3 or later.

Affected: >= 0Fixed in 1.3.3source →

CVE-2020-15095medium · fixedCVSS 4.4

npm CLI exposing sensitive information through logs

Versions of the npm CLI prior to 6.14.6 are vulnerable to an information exposure vulnerability through log files. The CLI supports URLs like `<protocol>://[<user>[:<password>]@]<hostname>[:<port>][:][/]<path>`. The password value is not redacted and is printed to stdout and also to any generated log files.

Affected: >= 0Fixed in 6.14.6source →

CVE-2019-16777high · fixedCVSS 7.7

npm Vulnerable to Global node_modules Binary Overwrite

Versions of the npm CLI prior to 6.13.4 are vulnerable to a Global node_modules Binary Overwrite. It fails to prevent existing globally-installed binaries to be overwritten by other package installations. For example, if a package was installed globally and created a `serve` binary, any subsequent installs of packages that also create a `serve` binary would overwrite the first binary. This will not overwrite system binaries but only binaries put into the global node_modules directory. This b

Affected: >= 0Fixed in 6.13.4source →

Inventory

Tools (5)

Click any tool to inspect its schema.

~155 tokens total

Community

Reviews

Be the first to review

Have you used this server?

Share your experience — it helps other developers decide.

How easy was setup?Did it work reliably?How was the documentation?

Frequently Asked Questions

Is io.github.SPAZIO-GENESI/attest-mcp-remote safe to use?: io.github.SPAZIO-GENESI/attest-mcp-remote has no known CVEs as of the latest MCPpedia security scan. It does not require authentication, so any local process can connect — keep this in mind in shared environments. Licensed under MIT.
How do I install io.github.SPAZIO-GENESI/attest-mcp-remote?: io.github.SPAZIO-GENESI/attest-mcp-remote supports copy-paste install configs on its MCPpedia page for Claude Desktop, Cursor, and Claude Code. Scroll to the Quick Install section and select your client.
What can io.github.SPAZIO-GENESI/attest-mcp-remote do?: io.github.SPAZIO-GENESI/attest-mcp-remote provides 5 tools: Status, Tools, Develop, Security, License. See the full tools list on the server page for descriptions and parameters.
What AI clients work with io.github.SPAZIO-GENESI/attest-mcp-remote?: io.github.SPAZIO-GENESI/attest-mcp-remote is compatible with claude-desktop, cursor, claude-code. It uses stdio transport.
Is io.github.SPAZIO-GENESI/attest-mcp-remote actively maintained?: io.github.SPAZIO-GENESI/attest-mcp-remote is actively maintained — last commit was 3 days ago.

Similar servers

Others in other

View all →

Transport Stdio95

Transport for TMCP using STDIO

197 14

Flare95

The graph based agentic IDE

123 3

Headroom95

Compress tool outputs, logs, files, and RAG chunks before they reach the LLM. 60-95% fewer tokens, same answers. Library, proxy, MCP server.

67.2k 3

app.fojin/fojin-mcp94

Buddhist canon tools: search, passages, cross-canon parallels, dictionaries — all URN-cited.

329 8

MCP Security Weekly

Get CVE alerts and security updates for io.github.SPAZIO-GENESI/attest-mcp-remote and similar servers.

Community

Discussion

Start a conversation

Ask a question, share a tip, or report an issue.

Has anyone used this with Cursor?How do you handle auth?Any alternatives?

Edit this pageView history

Other

Step 1

Install in your client

Config is the same across clients — only the file and path differ.

Supported in Claude Desktopstdio · Node 18+

Paste into ~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "io-github-spazio-genesi-attest-mcp-remote": {
      "args": [
        "-y",
        "npm"
      ],
      "command": "npx"
    }
  }
}

Are you the author?

Add this badge to your README to show your security score and help users find safe servers.

Embed in your READMEAbout badges →

[![MCPpedia Score](https://mcppedia.org/api/badge/io-github-spazio-genesi-attest-mcp-remote)](https://mcppedia.org/s/io-github-spazio-genesi-attest-mcp-remote)

Read me

What io.github.SPAZIO-GENESI/attest-mcp-remote does

Listed on the official MCP Registry as io.github.SPAZIO-GENESI/attest-mcp-remote.

Test This Server

Run this in your terminal to verify the server starts. Then let us know if it worked — your result helps other developers.

npx -y 'npm' 2>&1 | head -1 && echo "✓ Server started successfully"

After testing, let us know if it worked:

README

attest-mcp-remote

Listed on the official MCP Registry as io.github.SPAZIO-GENESI/attest-mcp-remote.

Remote MCP server (Streamable HTTP) for the Spazio Genesi digital-work attestation service. Zero install: add the URL as a connector in your MCP client and start verifying and attesting.

No file ever transits — by design. MCP has no reliable client→server file channel, and this service doesn't want one: every tool works on the SHA-256 fingerprint of the work. Agents with code execution compute it locally (sha256sum <file>), so the file never leaves the machine it lives on — not even through this server. For local-file tooling use the stdio package @spazio-genesi/attest-mcp; for humans, the website (in-browser hashing, full privacy) or the Telegram bot @SGAttestBot.

Status

In production. Live at https://attest-mcp-remote.it-e3f.workers.dev/mcp. All 8 tools implemented, tested, and validated end-to-end against production, including a real zero-install run from claude.ai (connector by URL, human Turnstile approval, certificate PDF issued and archived).

Tools

Tool	Auth	What it does
`service_status`	none	Health of worker / archive / signer / Bitcoin anchor
`check_anchor`	none	OpenTimestamps proof lookup for a fingerprint
`verify_attestation`	none	Verify the server HMAC signature of an attestation
`lookup_certificate`	none	Archive lookup + permanent links for a fingerprint
`authorize`	starts device flow	User approves once in the browser (anti-bot check)
`complete_authorization`	device flow	Claims the 24h session token (kept in session state, never echoed)
`attest_hash`	session token or API key header	Bind a fingerprint to a signed server timestamp
`create_certificate_pdf`	session-scoped	Generate + archive the certificate PDF, returns permanent links

Credentials: either the zero-config device flow above, or an Authorization: Bearer sg_k_… header on the connection (e.g. Claude Code: claude mcp add --transport http attest <url> --header "Authorization: Bearer sg_k_…"). Self-service keys: https://imgauth.spaziogenesi.org/developer/keys

Develop

npm install
npm run dev            # wrangler dev (default port 8787)
node test/smoke.mjs http://127.0.0.1:8787

test/smoke.mjs drives the Streamable HTTP transport end-to-end (initialize → tools/list → tools/call) against real, public production data (read-only). test/smoke-auth.mjs covers the credentialed flow and is a local-only harness: it needs an isolated imgauth wrangler dev (own --persist-to state, SIGNER_URL emptied) because the user-approval step is simulated by writing the local D1 directly — see the header comment in the file.

⚠️ When bumping the version

This server is also advertised through an MCP Server Card published by the web interface, which repeats this server's name, version and endpoint:

https://attestazione.spaziogenesi.org/.well-known/mcp/server-card.json
→ file: imgauthweb/.well-known/mcp/server-card.json

That file is not generated from this repository, so a version bump here silently makes it wrong. When you change version in package.json and server.json, update serverInfo.version in the card too — same release, same day. (Publishing a card that misstates the version is the same class of problem as an openapi.json left behind: a descriptor that lies is worse than none.)

Security

Report vulnerabilities → /sicurezza/ (responsible disclosure policy, safe harbor for good-faith research) — this repo has no security.txt of its own (Worker with no static assets), but the policy covers the whole project, including this workers.dev service.

License

MIT — © Spaz

... View full README on GitHub

Loading README…

Scored, not listed

Why this score

Five weighted categories — click any category to see the underlying evidence.

Score breakdown

88/100across 5 weighted dimensions

How we score →

0255075100

−12

Security

Maintenance

Efficiency

Documentation

Compatibility

Categoriesclick a row to see evidence

Security

OSV.dev

8 fixed

CVE-2022-29244high · fixedCVSS 7.5

Packing does not respect root-level ignore files in workspaces

Affected: >= 7.9.0Fixed in 8.11.0source →

CVE-2018-7408high · fixedCVSS 7.8

Incorrect Permission Assignment for Critical Resource in NPM

Affected: >= 0Fixed in 5.7.1source →

CVE-2013-4116low · fixed

Local Privilege Escalation in npm

Affected: >= 0Fixed in 1.3.3source →

CVE-2020-15095medium · fixedCVSS 4.4

npm CLI exposing sensitive information through logs

Affected: >= 0Fixed in 6.14.6source →

CVE-2019-16777high · fixedCVSS 7.7

npm Vulnerable to Global node_modules Binary Overwrite

Affected: >= 0Fixed in 6.13.4source →

Inventory

Tools (5)

Click any tool to inspect its schema.

~155 tokens total

Community

Reviews

Be the first to review

Have you used this server?

Share your experience — it helps other developers decide.

How easy was setup?Did it work reliably?How was the documentation?

Frequently Asked Questions

Is io.github.SPAZIO-GENESI/attest-mcp-remote safe to use?: io.github.SPAZIO-GENESI/attest-mcp-remote has no known CVEs as of the latest MCPpedia security scan. It does not require authentication, so any local process can connect — keep this in mind in shared environments. Licensed under MIT.
How do I install io.github.SPAZIO-GENESI/attest-mcp-remote?: io.github.SPAZIO-GENESI/attest-mcp-remote supports copy-paste install configs on its MCPpedia page for Claude Desktop, Cursor, and Claude Code. Scroll to the Quick Install section and select your client.
What can io.github.SPAZIO-GENESI/attest-mcp-remote do?: io.github.SPAZIO-GENESI/attest-mcp-remote provides 5 tools: Status, Tools, Develop, Security, License. See the full tools list on the server page for descriptions and parameters.
What AI clients work with io.github.SPAZIO-GENESI/attest-mcp-remote?: io.github.SPAZIO-GENESI/attest-mcp-remote is compatible with claude-desktop, cursor, claude-code. It uses stdio transport.
Is io.github.SPAZIO-GENESI/attest-mcp-remote actively maintained?: io.github.SPAZIO-GENESI/attest-mcp-remote is actively maintained — last commit was 3 days ago.