endpoint-validator
Deterministic API endpoint validation with pass/fail reporting.
Install / Use
npx skills add notque/vexjoy-agent --skill endpoint-validatorInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
OperationsSupported Platforms
Our assessment of endpoint-validator
endpoint-validator scores 82/100 on our quality scale, 633rd of 762 Operations skills we index.
Its SKILL.md is 4.2 KB long, well organised into 9 sections with 3 code examples: a solid amount of guidance for an agent.
It has 425 GitHub stars, a meaningful sign that others use it.
Maintenance, license and trust
- The repository was last updated 12 days ago, so endpoint-validator is actively maintained.
- It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
- Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
Safety scan
No issues foundOur scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands.
Automated pattern scan on 2026-10-15. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.
endpoint-validator compared with similar skills
All 4 of these similar skills score higher than endpoint-validator; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| endpoint-validator (this skill)by notque | 82 | 425 | 12d ago | SKILL.md |
| Agent-Reachby Panniantong | 100 | 97.6k | today | CLAUDE.md |
| headroomby headroomlabs-ai | 100 | 75.4k | today | CLAUDE.md |
| Scraplingby D4Vinci | 100 | 87.7k | today | MCP Server |
| crawl4aiby unclecode | 100 | 85.6k | today | MCP Server |
Frequently asked questions
- How do I install endpoint-validator?
- Run
npx skills add notque/vexjoy-agent --skill endpoint-validator. The install tabs above show the steps for each supported agent. - Which AI agents does endpoint-validator work with?
- It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is endpoint-validator safe to use?
- Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is endpoint-validator still maintained?
- The repository was last updated 12 days ago, so endpoint-validator is actively maintained.
Skill content
View source on GitHubname: endpoint-validator promoted_to: deploy description: "Deterministic API endpoint validation with pass/fail reporting." user-invocable: false allowed-tools:
- Bash
- Read
- Write
- Glob
- Edit
routing:
triggers:
- "validate endpoints"
- "smoke test API"
- "health check endpoints"
- "test endpoint"
- "check API"
- "smoke test" category: infrastructure not_for: "process/service uptime or daemon liveness (use service-health-check); only HTTP/API endpoint request validation" pairs_with:
- assessment
- testing
Endpoint Validator Skill
Deterministic HTTP endpoint validation: discover config, test each endpoint against expectations, report pass/fail with CI-compatible exit codes.
Deep References
Load on demand when the signal matches.
| Signal | Reference | Content |
|--------|-----------|---------|
| Security header WARNs, HSTS/CSP/X-Frame | references/security-headers.md | Header checks, required values, remediation |
| Config errors, hardcoded IPs, timeouts | references/endpoint-config-preferred-patterns.md | Configuration failure modes and fixes |
| 401/403 failures, auth patterns | references/auth-endpoint-patterns.md | Bearer, API-key, cookie auth validation |
Instructions
Phase 1: DISCOVER
Read repository CLAUDE.md for base URL conventions or env var names.
Search for endpoint config in order: endpoints.json in project root,
tests/endpoints.json, inline specification from user. Prefer version-controlled
config over ad-hoc lists.
Config shape:
{
"base_url": "http://localhost:8000",
"endpoints": [
{"path": "/health", "expect_status": 200},
{"path": "/api/v1/users", "expect_key": "data", "timeout": 10},
{"path": "/api/v1/search?q=test", "max_time": 2.0}
]
}
Endpoint fields: path (required), expect_status (default 200),
expect_key (top-level JSON key), timeout (default 5s), max_time (SLOW
threshold), method (default GET), headers (per-endpoint).
Rules:
- Warn before POST/PUT/DELETE against production base URLs.
- Use hostnames or
${ENV_VAR}inbase_url, not hardcoded IPs. - Confirm base URL reachable before the full suite.
Gate: config parsed, base URL reachable, at least one endpoint defined.
Phase 2: VALIDATE
Execute, do not reason. Run the request. Paste the exit code and output.
Test endpoints sequentially. For each:
- Send request with configured method and timeout.
- Check status code against
expect_status. Mismatch -> FAIL. - If
expect_keyset, parse JSON and check key exists. Missing/invalid -> FAIL. - If
max_timeset and elapsed exceeds it -> SLOW. - On non-localhost URLs, check security headers (HSTS, CSP, X-Content-Type-Options, X-Frame-Options). Missing -> WARN (not FAIL). Skip HSTS on HTTP-only base URLs. Skip X-Frame-Options if CSP has
frame-ancestors.
Failure handling: connection refused -> FAIL "Connection refused"; timeout -> FAIL "Timeout after Ns"; invalid JSON on expect_key -> FAIL "Invalid JSON response".
Gate: all endpoints tested, each has PASS/FAIL/SLOW verdict.
Phase 3: REPORT
Format:
ENDPOINT VALIDATION REPORT
==========================
Base URL: http://localhost:8000
/api/health 200 OK 45ms
/api/products 500 FAIL "Internal Server Error"
/api/slow 200 SLOW 3.2s > 2.0s threshold
SUMMARY: Passed 13/15 (86.7%), Failed 1, Slow 1
Exit 0 if all passed. Exit 1 if any failed.
Error Handling
| Error | Cause | Fix |
|---|---|---|
| Base URL unreachable | Wrong port or service down | ss -tlnp to confirm port |
| All endpoints timeout | Wrong host or proxy issue | curl -v a single endpoint |
| JSON parse failure on expect_key | Non-JSON response (HTML/XML) | Remove expect_key or check Content-Type |
| FAIL on intentional 404 | Default expect_status is 200 | Set "expect_status": 404 |
| 401 on auth endpoint | Missing/expired credentials | Add auth header; see references/auth-endpoint-patterns.md |
CI Integration
# Pre-deployment gate with curl
jq -r '.endpoints[].path' endpoints.json | while read path; do
curl -sf "http://localhost:8000$path" > /dev/null || { echo "FAIL: $path"; exit 1; }
done
Related Skills
Agent-Reach
97.6kGive your AI agent eyes to see the entire internet. Read & search Twitter, Reddit, YouTube, GitHub, Bilibili, XiaoHongShu — one CLI, zero API fees.
headroom
75.4kCompress tool outputs, logs, files, and RAG chunks before they reach the LLM. 20% fewer tokens for coding agents, 60-95% fewer tokens for JSON, same answers. Library, proxy, MCP server.
Scrapling
87.7k🕷️ An adaptive Web Scraping framework that handles everything from a single request to a full-scale crawl! Don't be shy, join here: https://discord.gg/EMgGbDceNQ and follow here for daily tips and tricks: https://x.com/Scrapling_dev
crawl4ai
85.6kOpen-source web crawler and scraper for LLMs and AI agents: any website into clean, LLM-ready Markdown. Run it yourself, or use Crawl4AI Cloud with one key.
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
