Back to Browse

Feason Context MCP Server

Developer ToolsLow Risk10.0MCP RegistryRemote
Free

Server data from the Official MCP Registry

Christian source evidence for AI agents, with provenance, tradition coverage, and citation checks.

About

Christian source evidence for AI agents, with provenance, tradition coverage, and citation checks.

Remote endpoints: streamable-http: https://www.feason.com/api/mcp

Security Report

10.0
Low Risk10.0Low Risk

Valid MCP server (1 strong, 0 medium validity signals). No known CVEs in dependencies. Imported from the Official MCP Registry.

Endpoint verified · Requires authentication · 1 issue found

Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.

Permissions Required

This plugin requests these system permissions. Most are normal for its category.

HTTP Network Access

Connects to external APIs or services over the internet.

file_system

Check that this permission is expected for this type of plugin.

env_vars

Check that this permission is expected for this type of plugin.

How to Connect

Remote Plugin

No local installation needed. Your AI client connects to the remote endpoint directly.

Add this to your MCP configuration to connect:

{
  "mcpServers": {
    "io-github-feason-com-context": {
      "url": "https://www.feason.com/api/mcp"
    }
  }
}

Documentation

View on GitHub

From the project's GitHub README.

Feason Context SDKs

Typed, dependency-free TypeScript and Python clients for the Feason Context REST API, plus its OpenAPI 3.1 contract.

Feason Context supplies source-grounded Christian research material with exact passages, provenance, stable citations, named tradition coverage, and explicit coverage boundaries. Applications decide how to use the returned evidence.

Included

  • typescript/@feason/context
  • python/feason-context
  • openapi/feason-context-openapi.yaml — the public REST contract
  • contract.json — versioned endpoint metadata used to generate both clients
  • server.json — official MCP Registry metadata for the hosted remote server
  • DIRECTORY_LISTING.md — reusable, boundary-aware MCP directory copy

The hosted service remains at https://www.feason.com. These clients do not contain the Feason corpus, production credentials, user data, retrieval engine, or server implementation. Tokens are accepted at runtime and are never persisted.

TypeScript

import { FeasonContextClient } from "@feason/context";

const client = new FeasonContextClient({ token: process.env.FEASON_CONTEXT_TOKEN! });
const packet = await client.evidencePacket({ question: "How did early Christians describe grace?" });
console.log(packet);

Python

import os
from feason_context import FeasonContextClient

client = FeasonContextClient(os.environ["FEASON_CONTEXT_TOKEN"])
packet = client.evidence_packet("How did early Christians describe grace?")
print(packet)

Development

node scripts/generate-clients.mjs --check
npm --prefix typescript install
npm --prefix typescript run build
npm --prefix typescript test
python3 -m unittest discover -s python -p 'test_*.py'

Distribution

The SDK package names are reserved in their manifests but are not advertised as publicly installable until their registry records are verified. See PUBLISHING.md for the release preflight and verification sequence.

The hosted MCP service is described separately by server.json. Directory descriptions should preserve Feason's evidence-layer boundaries; see DIRECTORY_LISTING.md.

Security

Do not place API tokens in source, examples, issues, or test fixtures. See SECURITY.md for private vulnerability reporting.

License

MIT. See LICENSE.

Reviews

No reviews yet

Be the first to review this server!