Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Bluesky Keyword Alerts

REMOTE · TELEMARK-APIFY-MONITORING-MCP.KATFU111111.WORKERS.DEV · SCANNED AUG 20

Search bounded public Bluesky keywords, handles, mentions, and hashtags.

Available components

remote · telemark-apify-monitoring-mcp.katfu111111.workers.dev 62
+3 this week 62 Trust /100
Trust breakdown (6 categories)

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. How we score →

Endpoint Security81
Transport & Reachability100
Schema Quality & AI Usability55
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 868 tokens (~868/item across 0 items; 0 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Nothing to assess: this server has no tools to check for usage examples. See how to fix → Fail
Stability & Change Management27
  • Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage0
  • Tool coverage not yet verified: we couldn't read the endpoint's tools.Unverified
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass

Unverified: 1 category

A category scored 0 because we could not verify it: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

remote · telemark-apify-monitoring-mcp.katfu111111.workers.dev

# add to Claude Code
claude mcp add --transport http telemarkdigital-publisher-bluesky-keyword-alerts https://telemark-apify-monitoring-mcp.katfu111111.workers.dev/bluesky
# ~/.codex/config.toml
[mcp_servers.telemarkdigital-publisher-bluesky-keyword-alerts]
url = "https://telemark-apify-monitoring-mcp.katfu111111.workers.dev/bluesky"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "telemarkdigital-publisher-bluesky-keyword-alerts": {
      "type": "remote",
      "url": "https://telemark-apify-monitoring-mcp.katfu111111.workers.dev/bluesky",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add telemarkdigital-publisher-bluesky-keyword-alerts --url https://telemark-apify-monitoring-mcp.katfu111111.workers.dev/bluesky --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  telemarkdigital-publisher-bluesky-keyword-alerts:
    url: "https://telemark-apify-monitoring-mcp.katfu111111.workers.dev/bluesky"
// mcp.json
{
  "mcpServers": {
    "telemarkdigital-publisher-bluesky-keyword-alerts": {
      "type": "http",
      "url": "https://telemark-apify-monitoring-mcp.katfu111111.workers.dev/bluesky"
    }
  }
}

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

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 20 Aug 26 0
    • This server's schema is too large to store in full, so we cannot compare its tools day to day functional
  • 19 Aug 26 +1
    • This server's schema is too large to store in full, so we cannot compare its tools day to day functional
  • 18 Aug 26 0
    • This server's schema is too large to store in full, so we cannot compare its tools day to day functional
  • 17 Aug 26 +1
    • This server's schema is too large to store in full, so we cannot compare its tools day to day functional
  • 16 Aug 26 0
    • This server's schema is too large to store in full, so we cannot compare its tools day to day functional
  • 15 Aug 26 +1
    • This server's schema is too large to store in full, so we cannot compare its tools day to day functional
  • 14 Aug 26 0
    • This server's schema is too large to store in full, so we cannot compare its tools day to day functional
  • 13 Aug 26 +1
    • Stability: unverified → 0.03 ▲ functional
    • This server's schema is too large to store in full, so we cannot compare its tools day to day functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 20 Aug 2026 · Probed https://telemark-apify-monitoring-mcp.katfu111111.workers.dev/bluesky

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=katfu111111.workers.dev CN=YE1,O=Let's Encrypt,C=US 29 Jul 2026 27 Oct 2026 ECDSA 256 ECDSA-SHA384 53df38beae7d58073c0d7286c5c05826755
SANs: *.katfu111111.workers.dev, katfu111111.workers.dev
CN=YE1,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 5ddd70dd31f801c85c186a7a04b80afe
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd
DNSSEC insecure

Validation of telemark-apify-monitoring-mcp.katfu111111.workers.dev. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
dev. present 60074 8 Verified
workers.dev. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Enforced and verified

The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.

Result Enforced and verified
Enforced On connection
HTTP status 401

WWW-Authenticate challenge Bearer realm="OAuth", error="invalid_token", error_description="Missing or invalid access token. Pass an Apify API token in the Authorization: Bearer <token> header. Manage tokens at https://console.apify.com/account/integrations", resource_metadata="https://telemark-apify-monitoring-mcp.katfu111111.workers.dev/.well-known/oauth-protected-resource/bluesky" 

Bearer realm="OAuth", error="invalid_token", error_description="Missing or invalid access token. Pass an Apify API token in the Authorization: Bearer <token> header. Manage tokens at https://console.apify.com/account/integrations", resource_metadata="https://telemark-apify-monitoring-mcp.katfu111111.workers.dev/.well-known/oauth-protected-resource/bluesky"
Header Value
content-security-policy default-src 'none'; frame-ancestors 'none'
x-content-type-options nosniff
x-frame-options DENY
referrer-policy no-referrer
www-authenticate Bearer realm="OAuth", error="invalid_token", error_description="Missing or invalid access token. Pass an Apify API token in the Authorization: Bearer <token> header. Manage tokens at https://console.apify.com/account/integrations", resource_metadata="https://telemark-apify-monitoring-mcp.katfu111111.workers.dev/.well-known/oauth-protected-resource/bluesky"

Protected resource metadata

Document https://telemark-apify-monitoring-mcp.katfu111111.workers.dev/.well-known/oauth-protected-resource/bluesky
Retrieved Yes
Resource https://telemark-apify-monitoring-mcp.katfu111111.workers.dev/bluesky
Authorisation server https://console-backend.apify.com
Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://telemark-apify-monitoring-mcp.katfu111111.workers.dev/bluesky Verified 200
http (plaintext) http://telemark-apify-monitoring-mcp.katfu111111.workers.dev/bluesky Inconclusive 401
MCP tools

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.

No tool schema has been captured from this endpoint yet.