Developer · Remote MCP server

Profusia

Give your AI a place to publish: living pages with live data, shareable links, no deploy pipeline.

Visit Profusia's website

What the MCP Registry states

The entry as published to the official MCP Registry (read 2026-10-04), latest version.

Registry name
ai.profusia/profusia
Version
0.1.0
Status
Active
Category
developer
Transport
Streamable HTTP
Published
2026-09-30
Updated
2026-09-30
Publisher
ai.profusia
Namespace
Namespace verified by the MCP Registry via the domain profusia.ai · how
Website
profusia.ai/connect
Source
Registry API entry

Remote endpoints

TransportURLHeaders declared
Streamable HTTPhttps://profusia.ai/mcpNone
Streamable HTTPhttps://{workspace}.profusia.ai/mcpNone

Live check

This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.

Endpoint
https://profusia.ai/mcp (HTTP)
Reachable
Yes (HTTP 401)
Handshake
Not completed: sign-in required
Sign-in required
Yes - HTTP 401; OAuth advertised (the answer points to its authorization metadata)
Checked on
2026-10-05
Endpoint
https://{workspace}.profusia.ai/mcp (HTTP)
Checked
Not requested: URL template placeholder
Checked on
2026-10-05

How the live check works

How to connect Profusia

Profusia is a remote MCP server: there is nothing to install. Its endpoints are https://profusia.ai/mcp and https://{workspace}.profusia.ai/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.

The URL contains placeholders to fill in before connecting: {workspace}.

No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.

Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect

More developer servers

All 5,152 →
ServerRunsEndpoint or package
prodreadyFree due diligence for your app, run by your coding agent. Then the full SDLC.Remote · HTTPLive check: sign-in requiredmcp.prodready.si
Product CliKnowledge graph CLI for managing features, ADRs, and test criteria as MCP-discoverable artifacts.Local · stdioMCP Bundle (.mcpb): Hafeok/product-cli/releases/download/v0.2.0/prod
ProfitCollector22 pay-per-call developer, security, network and data utilities using x402 on Base.Remote · HTTPLive check: ✓ handshakemcp.bakhour.ca
ProfitPlayMCP server for the live ProfitPlay BTC five-minute AI agent sandbox.Local · stdioOCI image (Docker): ghcr.io/jarvismaximum-hue/profitplay-mcp:0.1.0
Project BrainRead-only source search and retrieval across configured GitHub repositories.Local · stdioOCI image (Docker): ghcr.io/gentleelephant/project-brain:v2.0.3
Project ContextSafely manage repository-scoped issues across Linear, GitHub Issues, and Jira Cloud.Local · stdionpm: @sandovalrr/project-context-mcp
Project Memory MCPPersistent memory for AI coding agents - past bugs, decisions, and your corrections, in your repo.Local · stdionpm: @kaaustubh/project-memory-mcp
ProjectmemCoding agent memory - one local MCP server for every project. Warns before repeating failed fixes.Local · stdioPyPI: projectmem