Data · Remote MCP server
Context by Fulcra
Connect your Fulcra Context personal datastore: access your metrics, events, agent data and more.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
com.fulcradynamics/context- Version
- 1.0.2
- Status
- Active
- Category
- data
- Transport
- Streamable HTTP, stdio (local process)
- Package
- PyPI
- Published
- 2026-09-17
- Updated
- 2026-09-17
- Publisher
- com.fulcradynamics
- Namespace
- Namespace verified by the MCP Registry via the domain fulcradynamics.com · how
- Website
- fulcradynamics.com
- Repository
- github.com/fulcradynamics/fulcra-context-mcp
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://mcp.fulcradynamics.com/mcp | None |
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.
- 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
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| PyPI | fulcra-context-mcp | 0.3.3 | stdio |
How to connect Context by Fulcra
Context by Fulcra is a remote MCP server: there is nothing to install. Its endpoint is https://mcp.fulcradynamics.com/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.
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.
It can also run locally from a Python package published to PyPI: fulcra-context-mcp version 0.3.3. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Python; clients usually start it with uvx (from uv) or after pip install - the usual command is uvx fulcra-context-mcp.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"context": {
"command": "uvx",
"args": [
"fulcra-context-mcp"
]
}
}
}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 data servers
| Server | Runs |
|---|---|
| Content Intelligence API9 MCP tools: extract, analyze, research, compare, monitor, brief. Pay-per-call x402 or subscribe. | Remote · HTTPLive check: ✓ handshake |
| Content OptimizerSERP-based content scoring and optimization with 7 SEO categories. | Local · stdio |
| Content RabbitCreate, schedule, and publish social posts, manage accounts, and read analytics as MCP tools. | Remote & Local · HTTP, stdioLive check: sign-in required |
| Content Strategy APIFind rising topics before they peak across search and social. Free key at trendsapi.ai. | Remote · HTTPLive check: ✓ handshake |
| Context First MCP37-tool MCP server: context health, memory, reasoning, truthfulness & research pipeline. | Local · stdio |
| Context RelayCompact, citation-verifiable public web context for AI agents, paid per use with x402. | Remote · HTTPLive check: ✓ handshake |
| Contextq MCPPersistent memory, hybrid search and a goal graph for AI agents, over stdio or remote HTTP. | Remote & Local · HTTP, stdioLive check: sign-in required |
| Contract CompassKorean public procurement law: rule-engine rulings, statutes search, live court precedents. | Remote · HTTPLive check: ✓ handshake |