RDF Explorer

Created By
Emeka Azuka Okoyea year ago
A Model Context Protocol (MCP) server that provides the conversational interface for the exploration and analysis of RDF Turtle based Knowledge Graph in either Local File mode or SPARQL Endpoint mode.
Overview

What is RDF Explorer?

RDF Explorer is a Model Context Protocol (MCP) server that provides a conversational interface for exploring and analyzing RDF Turtle-based Knowledge Graphs in both Local File mode and SPARQL Endpoint mode.

How to use RDF Explorer?

To use RDF Explorer, set it up on Claude Desktop by configuring it to either a local RDF Turtle file or a SPARQL endpoint. You can then interact with the server using natural language queries to explore graph data.

Key features of RDF Explorer?

  • Execute SPARQL queries on local files or external endpoints.
  • Perform full-text searches on the graph.
  • Generate statistics and reports about the graph.
  • Analyze graph structure and find relationships.

Use cases of RDF Explorer?

  1. Exploring employee data in a corporate knowledge graph.
  2. Analyzing customer purchase patterns in a retail dataset.
  3. Generating reports on relationships within a semantic web dataset.

FAQ from RDF Explorer?

  • Can RDF Explorer handle large datasets?

Yes, RDF Explorer is designed to work with large RDF datasets efficiently.

  • Is RDF Explorer free to use?

Yes, RDF Explorer is open-source and free to use under the MIT License.

  • What types of queries can I run?

You can run SPARQL queries, full-text searches, and natural language queries to explore your data.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
Emeka Azuka Okoye
Star
-
Language
-
License
-
Category

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