OriginTrail DKG MCP Server (example)

Created By
OriginTraila year ago
Example python MCP server for DKG nodes
Overview

What is the OriginTrail DKG MCP Server?

The OriginTrail DKG MCP Server is an example Python server designed for connecting MCP-compatible agents with the OriginTrail Decentralized Knowledge Graph (DKG), facilitating the creation, retrieval, linking, and exchange of verifiable knowledge.

How to use the OriginTrail DKG MCP Server?

To use the server, clone the repository, install the necessary dependencies, configure environment variables, and run the server in either Stdio or SSE mode to interact with compatible clients.

Key features of the OriginTrail DKG MCP Server?

  • SPARQL Querying: Retrieve knowledge from the DKG using flexible SPARQL queries.
  • Knowledge Asset Creation: Convert natural language into structured JSON-LD and publish it to the DKG.
  • Agent Memory: Store and retrieve decentralized agent memory in a standardized way.
  • Interoperability: Compatible with various MCP clients like VS Code, Cursor, and Microsoft Copilot agents.

Use cases of the OriginTrail DKG MCP Server?

  1. Enabling agents to query the DKG for information.
  2. Allowing users to create and publish knowledge assets from natural language.
  3. Facilitating interoperability between different MCP-compatible tools and frameworks.

FAQ from the OriginTrail DKG MCP Server?

  • Is this server production-ready?

No, this is BETA software and not recommended for production use.

  • What programming language is used?

The server is built using Python.

  • Can I customize the server?

Yes, you can modify existing tools or add new functionality to tailor the server to your needs.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
OriginTrail
Star
0
Language
Python
License
-
Tags

Recommend Servers

View All
Payai X402 Tools

6 hours 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.

a day ago