Feason Context

io.github.Feason-comPublished by GitHub account Feason-comv7.0.0Updated Oct 24, 2026

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

VerifiedStreamable HTTPWeb executableWeb Search & ScrapingKnowledge & Memory

Overview

AI-generated overview

Hosted Feason Context MCP server that gives assistants source-grounded Christian research evidence with exact passages, provenance and citation checks.

What you can do
  • Retrieve source-grounded Christian research material with exact passages and provenance
  • Search the corpus and build evidence packets for a question
  • Evaluate claims, produce claim proofs and verify citations
  • Compare named traditions and see explicit coverage boundaries
  • Fetch a manifest describing the service's operations
When to use it
Useful when an assistant needs citable Christian source material, tradition comparisons, or verification that a claim or citation is backed by retrieved evidence, rather than free-form generated answers.
Requirements
A remote streamable HTTP endpoint at the provider's hosted service; OAuth authentication is required. No packages, environment variables or headers are declared in the manifest.
Before you install
Access requires OAuth sign-in to the hosted service, so queries and questions are sent to the provider. The service returns evidence only; applications decide how to use it, and verification failures or missing tradition coverage are reported explicitly. Keep any API tokens out of source, examples and issues.

Installation

In SourceWeft

  1. Open Feason Context in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.Feason-com%2Fcontext/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "feason-context": {
      "type": "http",
      "url": "https://www.feason.com/api/mcp"
    }
  }
}

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
  • USE_CASES.md — application recipes, operation selection, and response handling

Both clients expose seven REST operations: manifest, contextualize, claim evaluation, claim proof, search, evidence packets, and citation verification. The TypeScript SDK also composes them through FeasonStudyClient.study and compareTraditions. These helpers preserve retrieved evidence and report verification failures and missing tradition coverage explicitly.

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

ts
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

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

Development

sh
node scripts/generate-clients.mjs --checknpm --prefix typescript installnpm --prefix typescript run buildnpm --prefix typescript testpython3 -m unittest discover -s python -p 'test_*.py'

Distribution

This checkout tracks SDK source version 0.4.0 and the canonical seven-operation client contract. The OpenAPI document also describes separate Signed Proof V2 routes that these clients do not wrap. No package was published by this update, and registry availability has not been verified. Build or pack the source locally; 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.

Source: README.md at commit e4b4ffb

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v7.0.0LatestSep 16, 2026

Score

85% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts