List your agent

Purple8 — AI-Native Application Backend

MCP server● Hosted · onlinev0.72.1

Complete backend for AI-built apps: data, auth, workflows, SLAs, HITL & RAG in 176 MCP tools

What you can do with it

Share of each task's required capabilities it covers

Prefer a ready-made agent?

An MCP server is a connector for your own assistant. These finished products do the job for you: answer customer questions.
All AI agents to answer customer questions, ranked →

Similar tools

Listed for the same task: answer customer questions

Reviews

No review yet. Used Purple8 — AI-Native Application Backend? Be the first to help others choose.

What it does

Purple8 — AI-Native Application Backend is an MCP server, a connector that lets an AI assistant use it as a tool. It is hosted: an assistant connects to it over the internet, nothing to install.

From the publisher's description, Electra Index matched it to one capability: knowledge base qa. That makes it a candidate for tasks such as answer customer questions or answer questions from internal documents.

Facts come from the Official MCP Registry, as declared by the publisher. Capabilities are matched automatically (low confidence). None of this is a test of the tool.

At a glance

Hosted (remote)YES
Local installNO
Version0.72.1
PriceNot in the registry
First seen06 Nov 2026
Last checked6d ago

How to connect

As declared in the Official MCP Registry · hosted endpoint tested by Electra Index 2d ago (live check)

Hosted endpoints

  • https://purple8-graph-sandbox.fly.dev/mcp?profile=starter streamable-http
  • https://purple8-graph-sandbox.fly.dev/mcp/sse?profile=starter sse

Required: X-API-Key (get it from the publisher)

MCP settings (Claude Desktop, Cursor and other MCP clients)

{
  "mcpServers": {
    "purple8-hyper-graph": {
      "url": "https://purple8-graph-sandbox.fly.dev/mcp?profile=starter",
      "headers": {
        "X-API-Key": "<your X-API-Key>"
      }
    }
  }
}

Replace the values in <angle brackets>.

Live check

Electra Index connected to the hosted endpoint 2d ago

ONLINE Purple8 — AI-Native Application Backend answered an MCP connection on 12 Nov 2026 and introduced itself as purple8-hyper-graph 1.30.0 (MCP protocol 2025-06-18).

28 tools offered to AI assistants

  • rag.query · Flat Vector RAG — retrieves the most relevant graph nodes by pure vector similarity (HNSW + RRF fusion + keyword fallback), then calls the configured LLM to generate a grounded answer. Fastest of the three RAG modes (p50 ~45 ms, MRR 0.64);
  • rag.hybrid_query · Hybrid Graph-Vector RAG — fuses vector similarity AND graph structural signals at every stage: dual-seed fusion (Weighted RRF over vector rank + degree centrality), vector-guided BFS, and semantic path scoring. Highest accuracy: MRR 0.85, m
  • rag.profile_collection · Analyse the graph topology and return recommended RAG retrieval settings. Profiles node count, edge density, degree distribution, edge-type distribution, and embedding coverage, then derives concrete values for fusion_alpha, max_hops, seed_
  • graph.query · Execute a Cypher query against the Purple8 knowledge graph and return matching records. Use for nodes, edges, paths, or aggregated data.
  • graph.vector_search · Find the k nearest nodes to a natural-language query using the HNSW vector index.
  • graph.hybrid_search · Combine vector similarity with graph traversal for highest-recall retrieval. Best when graph structure matters.
  • graph.traverse · Walk the graph from a starting node following edges up to a given depth.
  • graph.add_node · Insert a new node into the graph (accepts `type`, `label`, or `node_type`). Requires editor role.
  • graph.add_edge · Create a directed edge (relationship) between two existing nodes. This is the primary agentic handoff mechanism — agents write their output as edges (e.g. DERIVED_FROM, RISK_ASSESSMENT, EXTRACTED_FROM) so downstream agents can discover work
  • graph.update_node · Update properties or labels on an existing node. Properties are merged with existing values (patch semantics — only the keys you supply are changed). Labels replace the full label set when provided. Use this to advance agent relay state, e.
  • graph.get_node · Retrieve a node and all its stored properties by ID.
  • data.ingest_text · Extract entities and relationships from raw text and write them into the graph. Calls preview first, then commits the complete extraction on success. auto_commit=false returns a review-only preview. Pending jobs return job_id for resumption
Show 16 more
  • data.commit · Commit a reviewed extraction or your own extractor's output without invoking DocIntel. Uses the complete POST /ingest/commit contract: entities, relationships, Markdown, spans, tables/pages, context, file_ref or inline file_bytes_b64 and in
  • journey.start · Create a new Journey Engine instance for an entity and move it to the first stage. All transitions are recorded as immutable graph edges. Requires editor role.
  • journey.advance · Advance a journey instance to the next stage. Actor and notes are written to the audit trail as an ADVANCED_TO edge. Requires editor role.
  • journey.status · Return the full state and audit trail for a journey instance — every stage transition, AI recommendation, and HITL decision.
  • journey.define · Define a new journey type (workflow template) with ordered stages, owner systems, and per-stage SLA policies. Once defined, instances can be started with journey.start. Call this first when building any new workflow — the agent can define t
  • journey.list · List journey instances with optional filters. Use this to discover what is in flight, find instances for a specific entity, or check all instances of a given type. Also returns all defined journey types when called with no arguments. Essent
  • journey.list_hitl · List pending Human-In-The-Loop (HITL) tasks — decisions that require a human (or agent acting as human proxy) to approve, reject, or escalate before the journey can continue. Returns task ID, title, assigned role, description, and the stage
  • journey.resolve_hitl · Resolve a Human-In-The-Loop (HITL) task — approve, reject, or escalate it. On approval the journey automatically advances to the next stage if advance_to_stage is set. The decision is written to the immutable graph audit trail with the acto
  • data.ingest_file · Send a document file (PDF, DOCX, PPTX, XLSX, HTML, IFC, CSV, …) to Purple8 DocIntel for parsing, entity extraction, and graph ingestion. The document is fetched by DocIntel from a public URL, not a local path. The complete extraction is com
  • graph.assert_statement · Idempotently assert one native RDF quad with exact lexical terms, explicit blank-node scope and optional graph name. Uses existing node/edge create and read permissions, record policies and API-key label restrictions. No bulk import or call
  • graph.semantic_query · Read-only indexed RDF/LPG pattern query with policy-filtered evidence. Use tagged rdf, lpg and lpg_edge patterns. Returns unified bindings and evidence or, with output_format=nquads, a JSON envelope containing selected asserted N-Quads and
  • graph.counts · Return the total number of nodes in the graph, optionally filtered by label. A cheap situational-awareness call an agent can make before deciding how to query or ingest.
  • graph.labels · List every node type (label) in the graph with how many nodes carry it, largest first. Cheap — O(types), not O(nodes). Call this first to learn what the graph contains (e.g. Person, Account, Invoice) before querying or filtering by label.
  • schema.validate · Validate the tenant's live graph data against the defined schema. Reports missing required properties, type/enum violations, edge source/target-type violations, and orphan labels (labels present in the graph but undefined in the schema). Re
  • schema.define_node_type · Define a new node type — the primitive that lets an agent build the data model itself. The type_name becomes the canonical label for nodes of this type. Set app_id to make the type a per-app IAM boundary (only matching API keys may touch it
  • schema.define_edge_type · Define a new edge (relationship) type. Constrain which node types may be the source/target, declare edge properties, and set cardinality (one_to_one | one_to_many | many_to_one | many_to_many). Fails 409 if the type already exists.

What "online" means: the server answered an MCP connection at the time of the check. It is not a guarantee of security, quality or continuous uptime. How we test: we open an MCP session and ask for the tool list, as an AI assistant would. We never run a tool and never send a key. Checked every few days. Method

Is this your server? Monitoring Pro: a check every 30 minutes and an email within the hour when it stops answering. Launch offer: $39.99 once, for life.

Facts & evidence

Each fact shows where it was seen and when.
FactValueEvidenceSourceLast confirmed
Version0.72.1DECLAREDSRC-001 Official MCP Registry6d ago
Hosted endpointhttps://purple8-graph-sandbox.fly.dev/mcp?profile=starter, https://purple8-graph-sandbox.fly.dev/mcp/sse?profile=starterDECLAREDSRC-001 Official MCP Registry6d ago
Local install (package)noDECLAREDSRC-001 Official MCP Registry6d ago
Remote access (hosted)yesDECLAREDSRC-001 Official MCP Registry6d ago
Websitehttps://www.purple8.ai/products/hyper-graph/DECLAREDSRC-001 Official MCP Registry6d ago
Registry statusactiveDECLAREDSRC-001 Official MCP Registry6d ago
MCP serveryesDECLAREDSRC-001 Official MCP Registry6d ago

Change history

  • VERSION06 Nov 2026
    0.72.0 → 0.72.1
  • NEW06 Nov 2026
    first seen in the index

Is this page accurate?

Flag it and our robot re-checks the official source. Reports never change a score.

Do you run Purple8 — AI-Native Application Backend? Know when it stops answering

For publishers · optional

Its hosted endpoint can be monitored. Monitoring Pro connects every 30 minutes like an AI assistant, emails you within the hour when it stops answering, keeps a 90-day availability history and adds your answer rate to your badge.

Monitor Purple8 — AI-Native Application BackendLaunch offer $39.99 once, for life instead of $9.99/month · All plans

Monitoring never changes a score or a rank.

Are you the publisher of Purple8 — AI-Native Application Backend?

Free · show your listing

An independent listing builds trust with your buyers. Announce it, and add the badge to your website or README.

Announce it on LinkedIn
Listed on Electra IndexListed on Electra Index
<a href="https://electraindex.com/mcp/purple8-hyper-graph?utm_source=badge&utm_medium=share&utm_campaign=listing"><img src="https://electraindex.com/api/badge/purple8-hyper-graph/card" width="260" height="72" alt="Listed on Electra Index"></a>

Questions about Purple8 — AI-Native Application Backend

How do I connect Purple8 — AI-Native Application Backend?

Use the hosted endpoint https://purple8-graph-sandbox.fly.dev/mcp?profile=starter in your assistant's MCP settings. The exact settings are in "How to connect" above, as declared in the Official MCP Registry.

Does Purple8 — AI-Native Application Backend need an API key or token?

Yes. The registry entry lists a required value: X-API-Key. Get it from the publisher.

What tools does Purple8 — AI-Native Application Backend offer?

When Electra Index connected on 12 Nov 2026, it listed 28 tools: rag.query, rag.hybrid_query, rag.profile_collection, graph.query, graph.vector_search, graph.hybrid_search, graph.traverse, graph.add_node and more. The full list is in "Live check" above.

Is Purple8 — AI-Native Application Backend online?

Yes. Its hosted endpoint answered an MCP connection from Electra Index 2d ago.

What can I use Purple8 — AI-Native Application Backend for?

Based on its description, it is most relevant to: answer customer questions, answer questions from internal documents, answer support phone calls, build a help center.