yake-server

yake-server provides a server wrapper around the YAKE (Yet Another Keyword Extractor) algorithm, exposing keyword extraction via an HTTP service (typically to extract keywords/keyphrases from text).

Evaluated Apr 04, 2026 (17d ago)
Homepage ↗ Repo ↗ Ai Ml nlp keyword-extraction yake server http api
⚙ Agent Friendliness
30
/ 100
Can an agent use this?
🔒 Security
38
/ 100
Is it safe for agents?
⚡ Reliability
10
/ 100
Does it work consistently?

Score Breakdown

⚙ Agent Friendliness

MCP Quality
0
Documentation
25
Error Messages
0
Auth Simplicity
50
Rate Limits
0

🔒 Security

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

Security posture is unknown from the provided prompt content. Since this is a generic server wrapper, security depends on the implementation (TLS termination, auth/rate limiting, input size validation, and whether logs accidentally capture full input text). Keyword extraction often processes user text, so careful logging/redaction is important to avoid leaking sensitive text.

⚡ Reliability

Uptime/SLA
0
Version Stability
0
Breaking Changes
0
Error Recovery
40
AF Security Reliability

Best When

You need quick keyword extraction and want to call a reusable HTTP service rather than embedding YAKE in every app.

Avoid When

You require advanced access control, tenant isolation, or clearly documented SLAs/error semantics from the server implementation.

Use Cases

  • Extracting keywords/keyphrases from user-provided text
  • Building lightweight NLP features without heavy ML model dependencies
  • Document classification support via keyword features
  • Search indexing/ranking enrichment using extracted keywords

Not For

  • Production deployment requiring strict enterprise-grade API governance (unless the server adds those features)
  • Use as a source of truth for semantic understanding beyond keyword extraction
  • Handling very large documents without considering server performance/memory limits

Interface

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

Authentication

OAuth: No Scopes: No

No authentication details were provided in the prompt content. Server likely runs without auth unless configured externally (not verifiable here).

Pricing

Free tier: No
Requires CC: No

Agent Metadata

Pagination
none
Idempotent
True
Retry Guidance
Not documented

Known Gotchas

  • Potential absence of explicit request/response schema (harder for agents to build correct calls).
  • If the server accepts free-form text without limits, agents may accidentally send very large payloads causing timeouts.
  • If no auth/rate limits are documented, agents may overload the service during retries or parallel calls.

Alternatives

Full Evaluation Report

Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for yake-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