io.github.wygogogo19/robotbase-dev
REMOTE · DEV.ROBOTBASE.CC
Agent MCP: 18 tools — GitHub/HF/npm/PyPI/HN trends plus 17 web tools for coding agents.
Available components
Last scanned (21 hours ago)
Scores higher than 4% of remote servers
Reachable. Last reached 4 Nov 2026.
Category Code Search and Documentation
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 → Why this is hard to score →
Endpoint Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 530, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport check failed: declared streamable-http, but the endpoint returned HTTP 530. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 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.
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.
- 4 Nov 26 −49
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: 0.37 → unverified ▼ security
- Authorization: partial → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Capabilities: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 26 +1
- Server version: 0.32.2 → 0.32.6 functional
- 27 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Oct 26 +1
- Server version: 0.32.0 → 0.32.2 functional
- 24 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 23 Oct 26 62
First indexed and scored.
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 4 Nov 2026 · Probed https://dev.robotbase.cc/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=robotbase.cc | CN=WE1,O=Google Trust Services,C=US | 28 Sept 2026 | 27 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 60447526cf6ab2960ea247fa7cc50202 |
| SANs: robotbase.cc, *.robotbase.cc | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of dev.robotbase.cc. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| cc. | present | 12593 | 13 | Verified |
| robotbase.cc. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|---|
| HTTP status | 530 |
| Header | Value |
|---|---|
| x-frame-options | SAMEORIGIN |
| referrer-policy | same-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://dev.robotbase.cc/mcp | HTTP error | 530 | |
| http (plaintext) | http://dev.robotbase.cc/mcp | Inconclusive | 530 |
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. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
dev_trending Dev Trending ~121
Developer ecosystem trends: GitHub repos, Hugging Face models, npm packages, PyPI stats and Hacker News. When to use: choosing a library/model, seeing what developers are adopting, checking package health. Do not use: for general web search (web_search) or social hot lists (social_hot). Returns: {ecosystem, items:[{name, metric, value, url, description, source}], errors}.
| Name | Type | Req | Description |
|---|---|---|---|
| ecosystem | string | – | – |
| limit | integer | – | – |
| query | string | – | Optional package/repo search term. |
No output schema declared.
No examples provided.
web_act Web Act ~287
Drive a real Chromium browser on one public page: click, type, press keys, scroll, wait for selectors, then return the resulting text (and optionally a screenshot and JSON XHR responses). When to use: the page needs interaction before its content appears (cookie banners, tabs, 'load more', form submit) and web_fetch/web_crawl cannot see it. Do not use: for plain reading (web_fetch) or bulk crawling (web_crawl); no login/paywall bypass. Returns: {ok, url, final_url, title, markdown, chars, elapsed_ms, screenshot?, xhr?, took_ms, _metering}. Max 10 actions; screenshot returns MCP image content. Metered: shares the web free bucket (100 calls/day per IP shared by all web tools), then 3 credits per call over x402.
| Name | Type | Req | Description |
|---|---|---|---|
| actions | array | yes | Actions: {type: click|type|press|scroll|wait_for|wait_ms, ...} |
| full_page | boolean | – | Full-page screenshot. Default false. |
| include_xhr | boolean | – | Return JSON XHR responses captured while acting. Default false. |
| max_chars | integer | – | Text cap 1000-20000. Default 20000. |
| screenshot | boolean | – | Return a JPEG screenshot. Default false. |
| url | string | yes | The http(s) page URL. |
No output schema declared.
No examples provided.
web_crawl Web Crawl ~255
Crawl one site's same-host pages starting from a URL (depth 1-2, at most 20 pages) and return each page's title, URL and readable text. When to use: you need several pages from one site (docs section, news index, product list) and web_map alone is not enough. Do not use: to mirror a whole site (hard cap 20 pages, same host), or for one page (web_fetch). Returns: {ok, url, final_url, count, pages:[{url, title, status, chars, content}], cached, took_ms, _metering}. Respects robots.txt and SSRF guards; partial page failures are skipped. Metered: shares the web free bucket (100 calls/day per IP shared by all web tools), then 3 credits per call over x402 - no API key.
| Name | Type | Req | Description |
|---|---|---|---|
| depth | integer | – | Link depth 1-2. Default 2. |
| max_chars | integer | – | Per-page content cap 200-4000. Default 1000. |
| max_pages | integer | – | Max pages 1-20. Default 20. |
| url | string | yes | Start URL (same host is crawled). |
No output schema declared.
No examples provided.
web_crawl_async Web Crawl Async ~251
Submit a same-host crawl as an asynchronous job and return a job_id immediately. When to use: you need more than a couple of pages and cannot hold a long HTTP request; submit here, then poll web_crawl_job until status is done, failed or cancelled. Do not use: for one page (web_fetch) or when you need the result in this call (web_crawl). Returns: {ok, job_id, status, url, depth, max_pages, max_chars, idempotent, poll_with}. Pass idempotency_key to retry safely (24h window returns the same job). Metered: shares the web free bucket (100 calls/day per IP), then 3 credits per submit over x402.
| Name | Type | Req | Description |
|---|---|---|---|
| depth | integer | – | Link depth 1-2. Default 2. |
| idempotency_key | string | – | Optional; retries within 24h return the same job. |
| max_chars | integer | – | Per-page content cap 200-4000. Default 1000. |
| max_pages | integer | – | Max pages 1-20. Default 20. |
| url | string | yes | Start URL (same host is crawled). |
No output schema declared.
No examples provided.
web_crawl_job Web Crawl Job ~176
Check or cancel an asynchronous crawl job created by web_crawl_async. When to use: after web_crawl_async, poll with action=status until status is done/failed/cancelled; use action=cancel to stop a running job. Do not use: to start a crawl (web_crawl_async) or for a quick one-page read (web_fetch). Returns status: {ok, job_id, status: queued|running|done|failed|cancelled, progress:{pages_done,max_pages}, created_at, updated_at, result?, error?}. Free (not metered); rate-limited. Done result uses the same shape as web_crawl.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | – | Poll status (default) or cancel the job. |
| job_id | string | yes | job_id returned by web_crawl_async. |
No output schema declared.
No examples provided.
web_diff Web Diff ~256
Fetch a page now and compare it with the previous snapshot of the same URL, returning whether it changed and a unified diff (no LLM). When to use: monitoring a page for updates - prices, docs, policy pages, SEO titles/meta; first call stores the baseline, later calls return added/removed lines. Do not use: for one-off reading (web_fetch) or structured fields (web_extract_schema). Returns: {ok, url, baseline, changed, diff, added_lines, removed_lines, previous_ts, current_ts, title, hash, chars, fetched_cached, took_ms, _metering}. fresh=true (default) adds a cache-busting query to bypass the 6h page cache; pass fresh=false to compare cached content. Snapshots are kept per URL in SQLite (latest only). Metered: shares the web free bucket (100 calls/day per IP), then 1 credit per call over x402.
| Name | Type | Req | Description |
|---|---|---|---|
| fresh | boolean | – | Bypass the page cache with a cache-busting query. Default true. |
| max_chars | integer | – | Compare at most this many chars (500-12000). Default 4000. |
| url | string | yes | The http(s) page URL. |
No output schema declared.
No examples provided.
web_extract Web Extract ~197
Extract structured data from one public page: tables (headers + rows), JSON-LD blocks, and Open Graph/Twitter/canonical/language metadata. When to use: the page has tables or schema.org JSON-LD you need as data, without an LLM. Do not use: when you only need the page text (web_fetch) or a screenshot (web_screenshot). Returns: {ok, url, final_url, title, meta:{description,image,site_name,type,canonical,lang}, jsonld[], tables:[{caption,headers,rows}], links? , cached, took_ms, _metering}. Metered: shares the web free bucket (100 calls/day per IP shared by all web tools), then 1 credit per call over x402.
| Name | Type | Req | Description |
|---|---|---|---|
| include_links | boolean | – | Also return same-host links (max 100). Default false. |
| url | string | yes | The http(s) page URL. |
No output schema declared.
No examples provided.
web_extract_schema Web Extract Schema ~242
Extract a page's structured data into a named schema's common fields (no LLM): article, product, event, faq, recipe, course, organization, local_business, breadcrumb, dataset or job_posting. When to use: you need fields (title/author/date, price/currency/availability, event dates, FAQ Q&A, recipe ingredients, org address) rather than raw markdown or tables. Do not use: to get every JSON-LD block verbatim (web_metadata/web_extract) or to read text (web_fetch). Returns: {ok, url, final_url, schema, requested_schema, detected_types, matched, fields:{...}, sources:[jsonld|meta], jsonld_count, tables_count, took_ms, cached, _metering}. If no matching JSON-LD exists it falls back to Open Graph/meta fields and matched=false. Metered: shares the web free bucket (100 calls/day per IP), then 1 credit per call over x402.
| Name | Type | Req | Description |
|---|---|---|---|
| schema | string | – | Target schema; auto detects from JSON-LD types. Default auto. |
| url | string | yes | The http(s) page URL. |
No output schema declared.
No examples provided.
web_feed Web Feed ~195
Read an RSS or Atom feed and return its latest items. When to use: the user wants the latest posts/news from a site that publishes a feed, or you found a feed URL and want headlines plus links. Do not use: to read article text (use web_fetch) or to discover a site's URLs (use web_map). Returns: {ok, url, final_url, title, count, items:[{title, link, published, summary}], cached, took_ms, _metering}. Summary is HTML-stripped and capped at 500 characters. Metered: shares the web free bucket (100 calls/day per IP shared by all web tools), then 1 credit per call over x402 - there is no API key.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max items to return, 1-20. Default 10. |
| url | string | yes | RSS/Atom feed URL (max 2048 chars). |
No output schema declared.
No examples provided.
web_fetch Web Fetch ~361
Fetch one public web page and return its readable text as clean markdown or plain text, with navigation, scripts, headers and footers stripped. When to use: you have a specific URL (from web_search or the user) and need what the page actually says - 'read this article', 'summarise this docs page', 'turn this URL into markdown'. Do not use: to crawl or mirror a site, to fetch a page behind a login or paywall, to read API/RPC endpoints, or for book text inside CyberLibrary (use cyberlibrary_get_chapter). Returns: {url, final_url, status, title, content, chars, truncated, fetched_at, source (direct|provider), cached, took_ms, _metering}. The response is capped at 12000 characters per call; raise max_chars (up to 20000) when you need more. Reads one public URL only, respects robots.txt, and does not bypass login or paywall. Direct fetch is tried first; pages blocked from this node are fetched through a provider and marked source=provider. Metered: all web tools share 100 free calls/day per IP (separate from the risk/library allowance), then 1 credit per call over x402 - there is no API key; the 402 answer carries accepts[].
| Name | Type | Req | Description |
|---|---|---|---|
| format | string | – | Output format. Default markdown. |
| max_chars | integer | – | Truncate the returned content to this many characters (2000-20000). Default 8000. |
| ocr | boolean | – | Force OCR on scanned PDFs/images (auto-detected by default; set false to skip). |
| url | string | yes | The http(s) URL to read (max 2048 chars). |
No output schema declared.
No examples provided.
web_fetch_batch Web Fetch Batch ~260
Fetch up to 5 public URLs in one call and return each page's title, engine and a short snippet (first ~1200 characters), so an agent can triage several links quickly. When to use: search returned several candidate pages and you want a first pass over all of them; then call web_fetch on the ones worth reading in full. Do not use: when you need the complete text of a page (use web_fetch), or to crawl a site (use web_map). Returns: {ok, count, ok_count, results:[{url, ok, final_url, status, title, engine, chars, snippet, error?}], took_ms, _metering}. Partial failures do not fail the whole call. Metered: counts one call per URL against the shared web free bucket (50 URLs/day per IP together with web_fetch), then 1 credit per URL over x402 - max 5 URLs per call, no API key.
| Name | Type | Req | Description |
|---|---|---|---|
| format | string | – | Snippet format. Default markdown. |
| max_chars | integer | – | Snippet length per page, 200-2000. Default 1200. |
| urls | array | yes | 1-5 http(s) URLs to fetch in one call. |
No output schema declared.
No examples provided.
web_map Web Map ~177
Discover the URLs of one site - sitemap first, then same-host links from the homepage. When to use: you need the list of pages a site exposes before fetching a few of them. Do not use: as a crawler (max 50 URLs, no page content) or to bypass robots.txt. Returns: {url, final_url, count, urls:[{url,source}], cached, took_ms, _metering}. Metered: shares the web free bucket (100 calls/day per IP shared by all web tools), then 1 credit per call over x402 - there is no API key; the 402 answer carries accepts[].
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max URLs to return, 1-50. Default 50. |
| url | string | yes | Site root or page URL (max 2048 chars). |
No output schema declared.
No examples provided.
web_metadata Web Metadata ~180
Extract a page's structured metadata: Open Graph, Twitter cards, canonical URL, language and JSON-LD. When to use: you need the title/description/author/image of a page, or JSON-LD structured data for a product/article, without reading the whole page. Do not use: when you need the page text (use web_fetch) or a screenshot (use web_screenshot). Returns: {ok, url, final_url, title, description, image, site_name, type, canonical, lang, jsonld[], cached, took_ms, _metering}. Metered: shares the web free bucket (100 calls/day per IP shared by all web tools), then 1 credit per call over x402 - there is no API key.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | The http(s) page URL (max 2048 chars). |
No output schema declared.
No examples provided.
web_monitor_delete Web Monitor Delete ~132
Delete one scheduled change monitor owned by the calling IP (its event history is removed too). When to use: the user no longer needs to watch a page, or the per-IP monitor limit was reached. Do not use: to pause a monitor temporarily - there is no pause; delete and re-create. Returns: {ok, deleted, monitor_id, note}; unknown or foreign ids return {ok:false,error:'monitor_not_found'} and delete nothing. Free (not metered); rate-limited to 20 calls/min per IP.
| Name | Type | Req | Description |
|---|---|---|---|
| monitor_id | string | yes | monitor_id returned by web_monitor_set. |
No output schema declared.
No examples provided.
web_monitor_list Web Monitor List ~237
List the scheduled change monitors owned by the calling IP, with latest/next check time, last title or error, and the 5 most recent change events. When to use: after web_monitor_set, poll this instead of re-fetching the page; or to show the user what is currently being watched. Do not use: to create a monitor (web_monitor_set) or to compare one page now (web_diff). Returns: {ok, count, monitors:[{monitor_id,url,interval_minutes,active,created_ts,last_check_ts,next_check_ts,last_title,last_error,webhook_enabled,events_total,recent_events}], note}. Pass monitor_id to get that one monitor plus last_event.diff (the most recent detected change, up to 4000 chars) so you can read what changed without a webhook. Free (not metered); rate-limited to 20 calls/min per IP.
| Name | Type | Req | Description |
|---|---|---|---|
| include_diff | boolean | – | With monitor_id, include the latest unified diff. Default true. |
| monitor_id | string | – | Optional: return this monitor (owned by the calling IP) plus its most recent change diff. |
No output schema declared.
No examples provided.
web_monitor_set Web Monitor Set ~362
Create a scheduled change monitor for one public URL: the server re-fetches the page on an interval, stores a new snapshot and records a diff event whenever the readable text changes. When to use: the user wants to be told when a page changes (price, docs, policy page, job post, release notes) and cannot poll it themselves; also for handing off 'watch this for me'. Do not use: for a single comparison right now (web_diff) or when you only need the page today (web_fetch). Returns: {ok, monitor_id, url, status:active, interval_minutes, next_check_ts, webhook_enabled, webhook_secret?, webhook_signature?, hint}. The first check runs within ~60s to store the baseline; later changes show up in web_monitor_list.recent_events and, if requested, are POSTed to webhook_url. Webhook: https only, no redirects, 8s timeout, up to 2 retries (30s/120s); body JSON {monitor_id,url,ts,changed,added_lines,removed_lines,title,diff,event_id}; verify header 'X-RobotBase-Signature: sha256=<hex HMAC-SHA256 of the raw body using webhook_secret>'. Limits: 15-1440 minutes; max 5 monitors per IP; monitors expire after 7 days. Metered: 1 credit (shares the web free bucket of 100 calls/day per IP).
| Name | Type | Req | Description |
|---|---|---|---|
| interval_minutes | integer | – | Check interval 15-1440 minutes. Default 60. |
| url | string | yes | The http(s) URL to watch (max 2048 chars). |
| webhook_url | string | – | Optional https endpoint notified on each change (HMAC-signed). |
No output schema declared.
No examples provided.
web_screenshot Web Screenshot ~258
Capture a screenshot of one public web page as an image (JPEG) plus metadata. When to use: visual layout matters - a dashboard, chart, UI state, or 'what does this page look like'. Do not use: to read text (use web_fetch), for pages behind a login or paywall, or for bulk capture. Returns: image content (image/jpeg) plus {url, final_url, title, width, height, bytes, engine, elapsed_ms, _metering}. Rendered by a real Chromium browser, robots.txt-respecting, SSRF-guarded, max 3MB per image. Metered: shares the web free bucket (100 calls/day per IP shared by all twelve web tools), then 2 credits per call over x402 - there is no API key; the 402 answer carries accepts[].
| Name | Type | Req | Description |
|---|---|---|---|
| full_page | boolean | – | Capture the whole page instead of the viewport. Default false. |
| height | integer | – | Viewport height 240-1200. Default 800. |
| url | string | yes | The http(s) URL to capture (max 2048 chars). |
| width | integer | – | Viewport width 320-1920. Default 1280. |
No output schema declared.
No examples provided.
web_search Web Search ~366
Search the live web and get ranked results with title, URL, snippet and published date. When to use: an agent needs current facts, news or links that are not on chain - 'what is the BTC fee market saying today', 'recent Zcash governance proposals', 'find the docs page for X'. Use it before web_fetch, then fetch the one URL that looks authoritative. Do not use: for on-chain facts (use the BTC/ETH/XMR/ZEC/TRON tools) or for content inside a CyberLibrary book (use cyberlibrary_fulltext_search). Provider: self-hosted SearXNG (Bing/Baidu/360/Sogou/Yandex/Marginalia) first, then Serper, Tavily and cn.bing RSS as automatic fallbacks. Returns: {query, count, results:[{title,url,snippet,published}], provider (serper|tavily|bing_rss), cached, took_ms, _metering}. Results may be cached for up to 10 minutes; a cached result still counts as one call against the free allowance. Metered: all web tools share 100 free calls/day per IP (separate from the risk/library allowance), then 1 credit per call over x402 - there is no API key; the 402 answer carries accepts[]. max count is 10.
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | – | Number of results to return, 1-10. Default 5. |
| freshness | string | – | Optional freshness filter. |
| lang | string | – | Optional language preference, e.g. zh-cn or en. |
| query | string | yes | Search query (1-200 characters). |
| site | string | – | Optional: restrict results to one domain, e.g. github.com. |
No output schema declared.
No examples provided.
How do I install the io.github.wygogogo19/robotbase-dev MCP server?
io.github.wygogogo19/robotbase-dev is a hosted endpoint at https://dev.robotbase.cc/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · dev.robotbase.cc
claude mcp add --transport http wygogogo19-robotbase-dev 'https://dev.robotbase.cc/mcp'
What is the io.github.wygogogo19/robotbase-dev MCP server?
io.github.wygogogo19/robotbase-dev is an MCP server listed in the public MCP registry as io.github.wygogogo19/robotbase-dev. Agent MCP: 18 tools, GitHub/HF/npm/PyPI/HN trends plus 17 web tools for coding agents. This page covers its hosted endpoint (https://dev.robotbase.cc/mcp).
Is the io.github.wygogogo19/robotbase-dev MCP server safe to use?
io.github.wygogogo19/robotbase-dev scores 18 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.wygogogo19/robotbase-dev MCP server expose?
io.github.wygogogo19/robotbase-dev exposes 18 tools: web_search, web_fetch, web_screenshot, web_map, web_fetch_batch, and 13 more. Their descriptions and schemas cost roughly 4,313 tokens of context every time the server is loaded.
Does the io.github.wygogogo19/robotbase-dev MCP server require authentication?
Its publisher declares no required credentials for io.github.wygogogo19/robotbase-dev. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the io.github.wygogogo19/robotbase-dev MCP server still maintained?
io.github.wygogogo19/robotbase-dev is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.