# Open Source Intelligence MCP (remote · oss-intel-mcp-production.up.railway.app)

GitHub project health, package dependency risk, trending repos, license & package comparison.

- Trust score: 62/100 (medium)
- Change this week: +2
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `oss-intel-mcp-production.up.railway.app`: 62/100 (this document), [markdown](https://verifymcp.io/servers/foundrynet-oss-intel-mcp/oss-intel-mcp-production.md), [page](https://verifymcp.io/servers/foundrynet-oss-intel-mcp/oss-intel-mcp-production)

## Channel facts

- Endpoint: `https://oss-intel-mcp-production.up.railway.app/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not yet verified: we couldn't confirm whether this endpoint requires it.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS not yet verified: we couldn't read the response headers to check for it.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 0/100
  - Transport check failed: declared streamable-http, but we couldn't connect to verify it.
- **Schema Quality & AI Usability**: 0/100
  - Schema not yet verified: we couldn't read the endpoint's schema.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 0/100
  - Tool coverage not yet verified: we couldn't read the endpoint's tools.
- **Capabilities**: 0/100
  - Capabilities not yet verified: we couldn't read the endpoint's capabilities.

**Unverified: 4 categories.** Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

## Install

### Claude

```bash
claude mcp add --transport http foundrynet-oss-intel-mcp https://oss-intel-mcp-production.up.railway.app/mcp
```

### Codex

```toml
[mcp_servers.foundrynet-oss-intel-mcp]
url = "https://oss-intel-mcp-production.up.railway.app/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "foundrynet-oss-intel-mcp": {
      "type": "remote",
      "url": "https://oss-intel-mcp-production.up.railway.app/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add foundrynet-oss-intel-mcp --url https://oss-intel-mcp-production.up.railway.app/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  foundrynet-oss-intel-mcp:
    url: "https://oss-intel-mcp-production.up.railway.app/mcp"
```

### Other

```json
{
  "mcpServers": {
    "foundrynet-oss-intel-mcp": {
      "type": "http",
      "url": "https://oss-intel-mcp-production.up.railway.app/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-01 (score 62, 0)

- [security regression] Endpoint reachability: reachable → unreachable

### 2026-07-31 (score 62, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 62, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-29 (score 62, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-28 (score 61, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-27 (score 60, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 60)

First indexed and scored.

## MCP tools (8)

### `project_health` (~195 tokens)

Check open-source project health for a GitHub repository — stars, forks,
open issues, commit frequency, last commit date, contributor count, license,
and a 0-100 composite health_score (popularity + activity + maintenance +
governance). The "is this project alive and worth depending on?" tool.
Source: GitHub API.

PAID: $0.01 per query after a daily free allowance (25/day). On a 402,
pay the returned payment challenge and re-call with the SAME args plus
payment_tx=<signature>. agent_id scopes your allowance; an Authorization:
Bearer fnet_ key bypasses it.

Input parameters:

- `agent_id`: stable id for your agent (scopes the free-tier counter).
- `payment_tx`: payment transaction signature, when re-calling after a 402.
- `repo` (string, required): GitHub repository as "owner/name", e.g. "facebook/react".

### `dependency_risk` (~197 tokens)

Analyze dependency vulnerability/risk for a software package — maintenance
status, last update, download trends, dependents, deprecation status, and a
0-100 risk_score (higher = riskier). The "should I add this dependency?" tool.
Sources: PyPI, npm registry, libraries.io.

PAID: $0.02 per query after the daily free allowance (25/day). On a
402, pay the returned payment challenge and re-call with the SAME args plus
payment_tx=<signature>. An Authorization: Bearer fnet_ key bypasses it.

Input parameters:

- `agent_id`: stable id for your agent (scopes the free-tier counter).
- `ecosystem` (string, required): npm | pypi | cargo.
- `package_name` (string, required): the package name, e.g. "express" or "requests".
- `payment_tx`: payment transaction signature, when re-calling after a 402.

### `trending_repos` (~206 tokens)

Find trending GitHub repositories with growth metrics (stars, forks,
language, license) — optionally filtered by language or topic. Unfiltered
queries are served from the daily-aggregated snapshot; filtered ones hit
GitHub search live. Source: GitHub API.

PAID: $0.01 per query after the daily free allowance (25/day). On a
402, pay the returned payment challenge and re-call with the SAME args plus
payment_tx=<signature>. An Authorization: Bearer fnet_ key bypasses it.

Input parameters:

- `agent_id`: stable id for your agent (scopes the free-tier counter).
- `language`: filter by primary language, e.g. "python", "rust".
- `payment_tx`: payment transaction signature, when re-calling after a 402.
- `period`: "daily" | "weekly" growth window (default weekly).
- `topic`: filter by GitHub topic, e.g. "machine-learning".

### `license_check` (~102 tokens)

Check open-source license compatibility for a GitHub repository — detected
license type, permissions, restrictions, commercial-use eligibility, and
compatibility guidance (permissive vs copyleft). Source: GitHub API. FREE.

Input parameters:

- `agent_id`: stable id for your agent (unused for free tools).
- `payment_tx`: unused (this tool is free).
- `repo` (string, required): GitHub repository as "owner/name", e.g. "facebook/react".

### `compare_packages` (~195 tokens)

Compare open-source packages (npm or PyPI) side by side in one ecosystem —
downloads, maintenance status, dependents (community size), deprecation,
license, and risk_score. The "which of these should I pick?" tool. Sources:
PyPI, npm registry, libraries.io.

PAID: $0.01 per query after the daily free allowance (25/day). On a
402, pay the returned payment challenge and re-call with the SAME args plus
payment_tx=<signature>. An Authorization: Bearer fnet_ key bypasses it.

Input parameters:

- `agent_id`: stable id for your agent (scopes the free-tier counter).
- `ecosystem` (string, required): npm | pypi | cargo (applies to all packages).
- `packages` (array, required): list of package names to compare (max 10).
- `payment_tx`: payment transaction signature, when re-calling after a 402.

### `daily_brief` (~250 tokens)

Get the curated daily open-source intelligence brief — the day's most
significant signals in one package: top trending repos, notable dependency
risks, newly deprecated packages, and the biggest-growth projects. From
GitHub, PyPI, npm, and libraries.io. Each brief carries a provenance
attestation so a buyer can verify it was produced by this server, unaltered.

PAID: $5 per brief. Defaults to today (UTC); a brief expires at the
next midnight UTC. On a 402, pay the returned payment challenge and re-call with
the SAME args plus payment_tx=<signature>. An Authorization: Bearer fnet_
key bypasses payment.

Input parameters:

- `agent_id`: stable id for your agent (scopes the free-tier counter).
- `date`: brief date YYYY-MM-DD (default today, UTC).
- `payment_tx`: payment transaction signature, when re-calling after a 402 (pay-per-query rail).
- `stripe_token`: Stripe Checkout Session id (cs_…), when re-calling after paying the Stripe payment link (alternative to x402). Can also be supplied via the X-Stripe-Token header.

### `brief_summary` (~165 tokens)

Get the top 5 signals from today's brief as structured JSON — a cheap
sample of the full daily_brief. Returns the day's highest-priority items
(no prose) so an agent can decide whether to buy the full brief.

PAID: $0.50 (vs the full daily_brief price). Defaults to today (UTC).
On a 402, pay the returned payment challenge and re-call with the SAME args plus
payment_tx=<signature>. An Authorization: Bearer fnet_ key bypasses payment.

Input parameters:

- `agent_id`: stable id for your agent (scopes the free-tier counter).
- `date`: brief date YYYY-MM-DD (default today, UTC).
- `payment_tx`: payment transaction signature, when re-calling after a 402.

### `mint_info` (~80 tokens)

FoundryNet Data Network info. FREE.

Returns how to attach a verifiable provenance attestation to your agent's
open-source analysis, and the sister data servers (gov-contracts,
brand-intel, patent-intel, financial-signals, weather-intel, cyber-intel,
compliance, academic-intel, fact-check, social-intel).

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/foundrynet-oss-intel-mcp/oss-intel-mcp-production#diagnostics

## Score history

- 2026-08-03: 62
- 2026-08-02: 62
- 2026-08-01: 62
- 2026-07-31: 62
- 2026-07-30: 62
- 2026-07-29: 62
- 2026-07-28: 61
- 2026-07-27: 60
- 2026-07-26: 60

## Links

- Remote endpoint: https://oss-intel-mcp-production.up.railway.app/mcp
- Repository: https://github.com/FoundryNet/oss-intel-mcp
- Changelog RSS feed: https://verifymcp.io/servers/foundrynet-oss-intel-mcp/oss-intel-mcp-production/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/foundrynet-oss-intel-mcp/oss-intel-mcp-production/changelog.json
- HTML version of this page: https://verifymcp.io/servers/foundrynet-oss-intel-mcp/oss-intel-mcp-production