Mcp Arcknowledge

Created By
dragonjumpa year ago
This MCP server conveniently lets you configure and interact across all your custom webhook endpoints from a config(knowledgebase json). You can manage new endpoint knowledge doc sources URLs.
Overview

What is MCP ArcKnowledge?

MCP ArcKnowledge is a Model Context Protocol (MCP) server designed for managing and querying custom webhook endpoints, allowing users to create a unified knowledge base.

How to use MCP ArcKnowledge?

To use MCP ArcKnowledge, clone the repository from GitHub, configure your knowledge document sources, and connect to the MCP server. You can then query the knowledge base with text questions.

Key features of MCP ArcKnowledge?

  • Manage and query multiple knowledge base endpoints in one configuration.
  • Register new document sources with URLs, descriptions, and API keys.
  • Aggregate results from multiple sources based on user queries.

Use cases of MCP ArcKnowledge?

  1. Centralizing knowledge management for various APIs.
  2. Querying specific knowledge bases for information retrieval.
  3. Integrating with AI tools for enhanced data processing.

FAQ from MCP ArcKnowledge?

  • Can I add multiple document sources?

Yes! You can register as many document sources as needed.

  • Is there a limit to the number of queries?

No, you can query the knowledge base as often as required.

  • What are the prerequisites for running MCP ArcKnowledge?

You need Go, Python 3.6+, and the Anthropic Claude Desktop app or similar.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
dragonjump
Star
-
Language
-
License
-

Recommend Servers

View All
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.

8 hours ago