Heimdall

Created By
shinzo-labsa year ago
Overview

what is Heimdall?

Heimdall is a lightweight service designed to manage local MCP (Model Context Protocol) servers, allowing users to easily configure and authorize tools for their MCP clients.

how to use Heimdall?

To use Heimdall, you can install it via NPX with a simple command or by downloading the package and running a setup script to configure your MCP servers.

key features of Heimdall?

  • Easy installation with a single command.
  • Centralized configuration for managing multiple MCP servers.
  • Ability to authorize specific tools for each MCP client.
  • Logging and troubleshooting support for running instances.

use cases of Heimdall?

  1. Managing configurations for multiple MCP servers in a development environment.
  2. Authorizing tools for different clients based on project requirements.
  3. Troubleshooting and logging for MCP server instances.

FAQ from Heimdall?

  • How do I install Heimdall?

You can install Heimdall using the command: npx @shinzolabs/heimdall setup.

  • Can I manage multiple MCP servers?

Yes! Heimdall allows you to manage multiple MCP servers from a single configuration.

  • What should I do if I encounter orphaned processes?

You may need to manually stop orphaned processes using the command: pkill -aif node.

Server Config

{
  "mcpServers": {
    "heimdall": {
      "command": "npx",
      "args": [
        "@shinzolabs/heimdall"
      ]
    }
  }
}
Project Info
Created At
a year ago
Updated At
a year ago
Author Name
shinzo-labs
Star
-
Language
-
License
-

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

16 hours ago
Voyei

6 hours ago