Provides cryptographic identity for AI agents using W3C DIDs, Verifiable Credentials, and post-quantum cryptography.
Also known as san-techie21/astracipher, @astracipher/core
- Stars
- 1
- Tools
- —
- Downloads, 30 days
- 128
- Latest version
- 0.1.1
- Last commit
- Sep 13, 2026
- License
- —
What is astracipher MCP?
astracipher provides cryptographic identity for AI agents using W3C DIDs, Verifiable Credentials, and post-quantum cryptography.
Summary generated from the project's README
About astracipher MCP server
Establishing cryptographic identity for AI agents is the primary function of astracipher. This server enables agents to utilize W3C Decentralized Identifiers (DIDs) and Verifiable Credentials to prove their identity and claims within a digital ecosystem. By integrating post-quantum cryptography, it ensures that agent identities remain secure even against future computational threats.
Developers can use this server to provide agents with a verifiable way to interact with other systems or users. The implementation focuses on standardizing how autonomous entities present themselves through established cryptographic protocols. This approach moves beyond simple API keys by providing a formal, verifiable framework for agent-based authentication and credential exchange.
Written from the project's README. Every use case is checked against a quote from it.
How to install astracipher MCP
Formats verified 10 Nov 2026Add to CursorAdd to GooseInstall astracipher MCP in Claude Code
$ claude mcp add astracipher -- npx -y @astracipher/coreInstall astracipher MCP in Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"astracipher": {
"command": "npx",
"args": [
"-y",
"@astracipher/core"
]
}
}
}Install astracipher MCP in VS Code
.vscode/mcp.json
{
"servers": {
"astracipher": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@astracipher/core"
]
}
}
}Install astracipher MCP in VS Code CLI
$ code --add-mcp '{"name":"astracipher","type":"stdio","command":"npx","args":["-y","@astracipher/core"]}'Install astracipher MCP in Claude Desktop
claude_desktop_config.json
{
"mcpServers": {
"astracipher": {
"command": "npx",
"args": [
"-y",
"@astracipher/core"
]
}
}
}Install astracipher MCP in Codex
$ codex mcp add astracipher -- npx -y @astracipher/coreInstall astracipher MCP in Codex config.toml
~/.codex/config.toml
[mcp_servers.astracipher] command = "npx" args = ["-y", "@astracipher/core"]
Install astracipher MCP in Gemini CLI
$ gemini mcp add -s user astracipher npx -- -y @astracipher/coreInstall astracipher MCP in Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"astracipher": {
"command": "npx",
"args": [
"-y",
"@astracipher/core"
]
}
}
}Automated checks
Ran Nov 14, 2026Full report →Passed our automated checks. That is not a security audit: read the code and give the server the narrowest access it needs. How checks work · What to fix for more points
- Source repository linked and reachablesan-techie21/astracipher is public and reachablegithub.com/san-techie21/astracipher ↗Pass
- Package names this repository as its source@astracipher/core names san-techie21/astracipher as sourcenpmjs.com/package/@astracipher/core ↗Pass
- Build provenance (Sigstore attestation)No build attestation published for this releaseNot checked
- Open source license (OSI)No licenseFinding
- Commit or release in the last yearLast commit or release 2026-09-13github.com/san-techie21/astracipher ↗Pass
- OpenSSF ScorecardNot checked
- Package name not close to a popular packageNo popular package one edit away from @astracipher/corePass
- No critical advisory in the package or its dependencies7 resolved dependencies checked; no critical advisoryosv.dev ↗Pass
- No hidden instructions to the model0 tool descriptions and the README read; no override phrases, credential paths or hidden charactersPass
- Destructive tools are labelledNot checked
- Remote endpoint answers the MCP handshakeNot checked
README
View on GitHubMCP Registry
The MCP registry provides MCP clients with a list of MCP servers, like an app store for MCP servers.
📤 Publish my MCP server | ⚡️ Live API docs | 👀 Ecosystem vision | 📖 Full documentation
Development Status
2025-10-24 update: The Registry API has entered an API freeze (v0.1) 🎉. For the next month or more, the API will remain stable with no breaking changes, allowing integrators to confidently implement support. This freeze applies to v0.1 while development continues on v0. We'll use this period to validate the API in real-world integrations and gather feedback to shape v1 for general availability. Thank you to everyone for your contributions and patience—your involvement has been key to getting us here!
2025-09-08 update: The registry has launched in preview 🎉 (announcement blog post). While the system is now more stable, this is still a preview release and breaking changes or data resets may occur. A general availability (GA) release will follow later. We'd love your feedback in GitHub discussions or in the #registry-dev Discord (joining details here).
Current key maintainers:
- Adam Jones (Anthropic) @domdomegg
- Tadas Antanavicius (PulseMCP) @tadasant
- Toby Padilla (GitHub) @toby
- Radoslav (Rado) Dimitrov (Stacklok) @rdimitrov
Contributing
We use multiple channels for collaboration - see modelcontextprotocol.io/community/communication.
Often (but not always) ideas flow through this pipeline:
- Discord - Real-time community discussions
- Discussions - Propose and discuss product/technical requirements
- Issues - Track well-scoped technical work
- Pull Requests - Contribute work towards issues
Quick start:
Pre-requisites
- Docker
- Go 1.24.x
- ko - Container image builder for Go (installation instructions)
- golangci-lint v2.4.0
Running the server
# Start full development environment
make dev-compose
This starts the registry at localhost:8080 with PostgreSQL. The database uses ephemeral storage and is reset each time you restart the containers, ensuring a clean state for development and testing.
Note: The registry uses ko to build container images. The make dev-compose command automatically builds the registry image with ko and loads it into your local Docker daemon before starting the services.
By default, the registry seeds from the production API with a filtered subset of servers (to keep startup fast). This ensures your local environment mirrors production behavior and all seed data passes validation. For offline development you can seed from a file without validation with MCP_REGISTRY_SEED_FROM=data/seed.json MCP_REGISTRY_ENABLE_REGISTRY_VALIDATION=false make dev-compose.
The setup can be configured with environment variables in docker-compose.yml - see .env.example for a reference.
Pre-built Docker images are automatically published to GitHub Container Registry:
# Run latest stable release
docker run -p 8080:8080 ghcr.io/modelcontextprotocol/registry:latest
# Run latest from main branch (continuous deployment)
docker run -p 8080:8080 ghcr.io/modelcontextprotocol/registry:main
# Run specific release version
docker run -p 8080:8080 ghcr.io/modelcontextprotocol/registry:v1.0.0
# Run development build from main branch
docker run -p 8080:8080 ghcr.io/modelcontextprotocol/registry:main-20250906-abc123d
Available tags:
- Releases:
latest,v1.0.0,v1.1.0, etc. - Continuous:
main(latest main branch build) - Development:
main-<date>-<sha>(specific commit builds)
Publishing a server
To publish a server, we've built a simple CLI. You can use it with:
# Build the latest CLI
make publisher
# Use it!
./bin/mcp-publisher --help
See the publisher guide for more details.
Other commands
# Run lint, unit tests and integration tests
make check
There are also a few more helpful commands for development. Run make help to learn more, or look in Makefile.
Architecture
Project Structure
├── cmd/ # Application entry points
│ └── publisher/ # Server publishing tool
├── data/ # Seed data
├── deploy/ # Deployment configuration (Pulumi)
├── docs/ # Documentation
├── internal/ # Private application code
│ ├── api/ # HTTP handlers and routing
│ ├── auth/ # Authentication (GitHub OAuth, JWT, namespace blocking)
│ ├── config/ # Configuration management
│ ├── database/ # Data persistence (PostgreSQL)
│ ├── service/ # Business logic
│ ├── telemetry/ # Metrics and monitoring
│ └── validators/ # Input validation
├── pkg/ # Public packages
│ ├── api/ # API types and structures
│ │ └── v0/ # Version 0 API types
│ └── model/ # Data models for server.json
├── scripts/ # Development and testing scripts
├── tests/ # Integration tests
└── tools/ # CLI tools and utilities
└── validate-*.sh # Schema validation tools
Authentication
Publishing supports multiple authentication methods:
- GitHub OAuth - For publishing by logging into GitHub
- GitHub OIDC - For publishing from GitHub Actions
- DNS verification - For proving ownership of a domain and its subdomains
- HTTP verification - For proving ownership of a domain
The registry validates namespace ownership when publishing. E.g. to publish...:
io.github.domdomegg/my-cool-mcpyou must login to GitHub asdomdomegg, or be in a GitHub Action on domdomegg's reposme.adamjones/my-cool-mcpyou must prove ownership ofadamjones.mevia DNS or HTTP challenge
Community Projects
Check out community projects to explore notable registry-related work created by the community.
More documentation
See the documentation for more details if your question has not been answered here!
astracipher MCP questions
How do I add astracipher MCP to Claude Code?
Run claude mcp add astracipher -- npx -y @astracipher/core in your terminal. Add --scope user to make it available in every project.
How do I add astracipher MCP to Cursor?
Open ~/.cursor/mcp.json and add the server under mcpServers, using the Cursor config shown in the install section above.