tagesschau-mcp-server

Provides an MCP server that surfaces tagesschau.de news content to an MCP-capable client/agent, including retrieval of latest articles and fetching details for a specific article (by URL).

Evaluated Apr 04, 2026 (16d ago)
Repo ↗ Communication mcp news rss-like go tooling tagesschau information-retrieval
⚙ Agent Friendliness
42
/ 100
Can an agent use this?
🔒 Security
36
/ 100
Is it safe for agents?
⚡ Reliability
28
/ 100
Does it work consistently?

Score Breakdown

⚙ Agent Friendliness

MCP Quality
45
Documentation
40
Error Messages
0
Auth Simplicity
90
Rate Limits
10

🔒 Security

TLS Enforcement
50
Auth Strength
30
Scope Granularity
20
Dep. Hygiene
40
Secret Handling
40

From the provided content, there is no explicit mention of TLS settings, authentication, authorization scopes, or secret handling practices. Because it is a local MCP server binary, security depends on the deployment pattern and any environment variables/config not shown here. Upstream access (tagesschau API) may require additional safeguards not documented in the README.

⚡ Reliability

Uptime/SLA
0
Version Stability
35
Breaking Changes
50
Error Recovery
25
AF Security Reliability

Best When

You want an agent-accessible news retrieval tool scoped specifically to tagesschau.de and can run a local/hosted MCP server binary.

Avoid When

You need a documented, contract-stable API surface (versioned tool schemas, explicit error codes, pagination parameters) or a hosted SaaS endpoint with published operational guarantees.

Use Cases

  • Letting an AI agent browse tagesschau.de for the latest headlines by category
  • Enabling an agent to answer questions about a specific tagesschau article by fetching its details
  • News aggregation/workflows that need structured access to latest articles and article metadata

Not For

  • Use as a general-purpose web scraping framework for arbitrary sites
  • Use where strict guarantees about data freshness, completeness, or editorial accuracy are required
  • Production deployments without verifying the MCP tool schema, runtime behavior, and upstream API constraints

Interface

REST API
No
GraphQL
No
gRPC
No
MCP Server
Yes
SDK
No
Webhooks
No

Authentication

OAuth: No Scopes: No

No authentication requirements are described in the provided README. MCP tool permissions/security are not documented in the supplied content.

Pricing

Free tier: No
Requires CC: No

No pricing information provided; appears to be self-hosted (MIT-licensed Go binary).

Agent Metadata

Pagination
none
Idempotent
False
Retry Guidance
Not documented

Known Gotchas

  • README does not describe MCP tool names, parameters, output schemas, or pagination/limits; agent integration may require inspecting the source code.
  • No stated guidance for handling upstream failures/rate limits/timeouts from the underlying tagesschau content API.
  • No example MCP request/response payloads; tool contract may differ from the high-level description.

Alternatives

Full Evaluation Report

Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for tagesschau-mcp-server.

AI-powered analysis · PDF + markdown · Delivered within 30 minutes

$99

Package Brief

Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.

Delivered within 10 minutes

$3

Score Monitoring

Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.

Continuous monitoring

$3/mo

Scores are editorial opinions as of 2026-04-04.

8642
Packages Evaluated
17761
Need Evaluation
586
Need Re-evaluation
Community Powered