# Social Trends Intelligence MCP (remote · social-intel-mcp-production.up.railway.app)

Trending topics, cross-platform sentiment, viral content, community pulse & brand mentions.

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

## Components

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

## Channel facts

- Endpoint: `https://social-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-social-intel-mcp https://social-intel-mcp-production.up.railway.app/mcp
```

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

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

### Other

```json
{
  "mcpServers": {
    "foundrynet-social-intel-mcp": {
      "type": "http",
      "url": "https://social-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-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)

- [security regression] Endpoint reachability: reachable → unreachable
- [security regression] Stability: 0.10 → unverified
- [security regression] HSTS header: fail → unverified
- [security regression] Transport: pass → fail
- [security] Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it.
- [functional regression] Tool coverage: 100 → unverified
- [functional regression] Capabilities: pass → unverified
- [functional] First check of Schema quality: unverified

### 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)

### `trending_topics` (~150 tokens)

Track trending topics across social media with velocity scores — what's
gaining attention right now on Reddit, Hacker News, and Google Trends.

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

Input parameters:

- `agent_id`: stable id for your agent (scopes the free-tier counter).
- `category`: optional keyword filter for topics.
- `payment_tx`: payment transaction reference, when re-calling after a 402.
- `platform`: reddit | hackernews | all (default all).

### `topic_sentiment` (~163 tokens)

Analyze cross-platform sentiment for a topic on Reddit and Hacker News —
an overall score + per-platform breakdown, volume trend (rising/steady/new),
and key discussion threads. Deterministic lexicon heuristic (no LLM).

PAID: $0.01 per query after the daily free allowance (25/day). On a
402, follow the returned payment instructions and re-call with the SAME
args plus payment_tx=<reference>. 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 reference, when re-calling after a 402.
- `topic` (string, required): the topic/keyword to gauge sentiment for.

### `viral_content` (~166 tokens)

Track viral content gaining traction fastest on Reddit and Hacker News —
posts and stories ranked by velocity (engagement per hour since posting), the
"what's about to blow up?" tool.

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

Input parameters:

- `agent_id`: stable id for your agent (scopes the free-tier counter).
- `hours_back`: only content posted in the last N hours.
- `min_score`: minimum upvotes/points to include.
- `payment_tx`: payment transaction reference, when re-calling after a 402.

### `community_pulse` (~184 tokens)

Check the pulse of a community on Reddit or Hacker News — its hot topics,
aggregate sentiment, and activity level (high/moderate/low by total
engagement). Point it at a subreddit, a Hacker News topic, or both.

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

Input parameters:

- `agent_id`: stable id for your agent (scopes the free-tier counter).
- `hn_topic`: a keyword to pulse on Hacker News.
- `payment_tx`: payment transaction reference, when re-calling after a 402.
- `subreddit`: a subreddit name, e.g. "technology" (no r/ needed).

### `brand_mentions` (~168 tokens)

Track brand mentions across Reddit and Hacker News with sentiment + context —
who's talking about a brand or product, where, how they feel, and the threads
driving it. Premium.

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

Input parameters:

- `agent_id`: stable id for your agent (scopes the free-tier counter).
- `brand` (string, required): the brand/product/company name to track.
- `days_back`: lookback window in days (default ~7).
- `payment_tx`: payment transaction reference, when re-calling after a 402.

### `daily_brief` (~242 tokens)

Get the curated daily social-trends brief from Reddit, Hacker News, and
Google Trends — the day's most significant signals in one package: top trending
topics, fastest-moving viral content, sentiment shifts by platform, and the
most-active communities. Each brief carries a verifiable provenance
attestation so a buyer can confirm 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, follow the returned payment instructions and
re-call with the SAME args plus payment_tx=<reference>. 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 reference, when re-calling after a 402.
- `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` (~168 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, follow the returned payment instructions and re-call with the
SAME args plus payment_tx=<reference>. 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 reference, when re-calling after a 402.

### `mint_info` (~85 tokens)

Get FoundryNet Data Network info + attestation details. FREE.

Returns how to attest your agent's social-trends analysis for verifiable
provenance, and the sister data servers (gov-contracts, brand-intel,
patent-intel, financial-signals, weather-intel, cyber-intel, compliance,
academic-intel, fact-check, oss-intel).

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/foundrynet-social-intel-mcp/social-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://social-intel-mcp-production.up.railway.app/mcp
- Repository: https://github.com/FoundryNet/social-intel-mcp
- Changelog RSS feed: https://verifymcp.io/servers/foundrynet-social-intel-mcp/social-intel-mcp-production/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/foundrynet-social-intel-mcp/social-intel-mcp-production/changelog.json
- HTML version of this page: https://verifymcp.io/servers/foundrynet-social-intel-mcp/social-intel-mcp-production