Data · Remote MCP server
Feason Context
Christian source evidence for AI agents, with provenance, tradition coverage, and citation checks.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.Feason-com/context- Version
- 7.0.0
- Status
- Active
- Category
- data
- Transport
- Streamable HTTP
- Published
- 2026-09-02
- Updated
- 2026-09-02
- Publisher
- Feason-com (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/Feason-com) · how
- Website
- www.feason.com/developers
- Repository
- github.com/Feason-com/feason-context
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://www.feason.com/api/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
How to connect Feason Context
Feason Context is a remote MCP server: there is nothing to install. Its endpoint is https://www.feason.com/api/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.
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 |
|---|---|
| Fbi Wanted MCPFBI Wanted API: most wanted list, search, and top rewards. No key required. | Local · stdio |
| FccFCC public geo/census APIs (geo.fcc.gov) MCP. | Remote · HTTPLive check: ✓ handshake |
| Fcc Broadband MCP ServerFCC broadband availability, coverage analysis, and digital divide data for US geographies. | Remote & Local · HTTP, stdioLive check: ✓ handshake |
| Fcc MCPFCC Census Block API: find census block, state, county and tract for coordinates. | Local · stdio |
| Federal Compass MCPAI compass from private sector to federal career - USAJobs search, salary, KSA. | Local · stdio |
| Federal Regulations MCP ServerSearch and trace US federal rules across the Federal Register, eCFR, and Regulations.gov. | Remote & Local · HTTP, stdioLive check: ✓ handshake |
| Federal Reserve MCP ServerSearch and fetch ~800K Federal Reserve economic time-series from the FRED API via MCP. | Local · stdio, HTTP |
| Fedlex ConnectorSearch Swiss federal legislation: laws, articles, amendments via the Fedlex SPARQL endpoint. | Remote · HTTPLive check: ✓ handshake |