Proofmark Demo Server
io.github.SamuelDharshiPublished by GitHub account SamuelDharshiv1.0.0Updated Nov 7, 2026
A small filesystem MCP server used to demonstrate Proofmark attestation.
The publisher's own server: demo.st
Overview
A small local filesystem MCP server, distributed as an npm package, used to demonstrate Proofmark attestation.
- What you can do
- The input lists no tools. The registry description calls it a small filesystem MCP server used to demonstrate Proofmark attestation, so it is presumably meant to expose basic file or directory operations to an assistant.
- No tool names, parameters or behaviors are documented, and no README or server instructions are provided, so the exact capabilities cannot be confirmed from this listing.
- When to use it
- Only worth adding if you specifically want to try out or illustrate Proofmark attestation with a minimal filesystem server; for real file work, choose a server with documented tools.
- Requirements
- Runs as a local process over stdio, installed from the npm package proofmark-demo-server, so Node.js and npm are needed. No authentication, environment variables or headers are declared. Desktop client only; not available as a web executable.
Installation
In SourceWeft
- Open Proofmark Demo Server in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
This repository has no README.
Tools
0Version history
1- v1.0.0LatestNov 7, 2026
Score
25% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
- License10 pts
Declare a license in the repository or the registry entry.
Other Demo integrations
demo.st
st.demoOfficial publisher
A remote MCP server for demo.st that lets an assistant reserve a subdomain, publish a zipped static site, and manage a small document store for it.
PlanPro demo (unofficial, AetherStack)
Published by GitHub account piksliviksi
Unofficial demo MCP endpoint exposing PlanPro-style work plans, KPIs and risks over synthetic data, with OAuth sign-in.
WebMCP Demo Store
Published by GitHub account kamatanuj
A demo online store exposed as MCP tools, letting an assistant search a product catalog, manage a cart and place orders without scraping HTML.
Everyday Software Voice Demo
Published by GitHub account PpiNeaPpLe
A remote MCP server that builds a prefilled link for trying a browser-based AI receptionist demo from a public business website.
Mcp Ticket Demo
Published by GitHub account markusvankempen
A reference MCP ticket-desk server for learning and demoing MCP, with 19 tools, resources, prompts, auth modes, PII gating and rate limiting.