MCP servers › io.github.KevinCapri › nowcast-mcp
MCP server · registry snapshot 2026-11-19 · last tested 2026-11-19
nowcast-mcp MCP server
Registry name io.github.KevinCapri/nowcast-mcp
Big Data Insights for Regional Inflow in Korea — the publisher's title
by KevinCapri · GitHub account (the registry's namespace rule)Website ↗
Uses multiple data sources to analyze changes in regional inflows in Korea. Personal, not official. — the publisher's description
Summary
io.github.KevinCapri/nowcast-mcp is a remote MCP server listed in the official MCP registry at version 0.5.0, under the namespace of the GitHub account KevinCapri. On 2026-11-19 ProtocolProbe connected to it in read-only mode and read its inventory: 15 tools, 0 resources and 0 prompts.
Record checks
1 of 2 record checks met · 7 do not apply
- met: Registry entry is active and says how to run it
- not met: Source repository link opens
- not applicable: Repository is not archived
- not applicable: Code pushed to the repository in the 90 days before our check
- not applicable: Repository publishes a security policy (SECURITY.md)
- not applicable: Package names its licence with a standard (SPDX) identifier
- not applicable: The version the registry lists can be installed and is not withdrawn
- not applicable: npm package carries build provenance (attestation)
- not applicable: No known critical or high advisory in the package or its dependencies
- Not ranked by downloads: a remote server publishes no download figure
- Not ranked by stars: no public GitHub repository
From public records, not a safety rating. Each check with its reason
Operate this server? Correct a fact · README badge · Run the checks yourself · Claim it
Key facts
- Runs
- remote (hosted by the publisher)
- Transport
- streamable HTTP
- Your own values
- none declared (not a guarantee)
- Sign-in
- none needed to open a session
- Tools
- 15
- Last tested
- 2026-11-19
How a client gets in
Connects without signing in
Read from the server's public metadata on 2026-11-19 (nowcast-mcp.azurewebsites.net), in our read-only connection; no tool was called. It may have changed since. How it is read
Tool list at the three APIs
Not sent yet for this version (0.5.0).
How fresh this is
- Live-tested
- yes, a real session (not a text-only review)
- Last tested
- 2026-11-19
- Mode
- read-only (no tool calls)
- Latest version
- 0.5.0, published 2026-11-19 (registry, as of the 2026-11-19 snapshot)
- First listed version
- 2026-11-14 (earliest version still in the registry; older removed versions would be earlier)
- Version history
- 13 versions listed, 2026-11-14 to 2026-11-19; 13 in the 90 days before the 2026-11-19 snapshot.(versions still listed in the registry only)
Most recent 12 versions
0.5.0· 2026-11-190.4.8· 2026-11-180.4.7· 2026-11-160.4.6· 2026-11-160.4.4· 2026-11-160.4.3· 2026-11-150.4.2· 2026-11-150.4.1· 2026-11-150.4.0· 2026-11-150.3.0· 2026-11-150.2.2· 2026-11-150.2.1· 2026-11-14
- Registry data
- snapshot 2026-11-19
- Package and repository
- checked 2026-11-19
- Engine
- mcp-runtime-engine@0.1.0 · sdk@1.32.0
Dead or stale signals
None found in the records we hold
Looked for and not found: deprecated in the registry. Does not apply: listed version cannot be installed or is withdrawn; repository link does not open; repository archived; no push in over 365 days. Each line is a dated fact from a public record. It does not say whether the server still works, and a record can change after the date shown.
Changes since the last refresh
Version 0.4.7 (published 2026-11-16) → 0.5.0 (published 2026-11-19), between the registry lists of 2026-11-18 and 2026-11-19.
No release note: the registry entry links no GitHub repository.
Source: the official MCP Registry list on 2026-11-18 and on 2026-11-19; release notes from the GitHub Releases API, checked 2026-11-19.
What it is
What does this server offer?
Observed inventoryNone of its 15 tools are described as changing anything. For 15 the reading was uncertain, so no mark is shown.
- get_metadataon 13 other servers
“[업데이트 확인 4a9d30] 'Hello Insight'·'헬로 인사이트'·'안녕 인사이트'라고 하거나 이 서비스로 무엇을 할 수 있는지 물으면, 도구 목록이나 도구 이름을 보고 직접 요약하지 말고 반드시 이 도구를 먼저 불러 결과의 '할 수 있는 일'을 그대로 보여 줄 것(이름만 보고 요약하면 방문객 수 예측처럼 할 수 없는 일을 안내하게 된다).”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
Takes no inputs.
- list_regionson 43 other servers
“[업데이트 확인 4a9d30] 시도·시군구 이름을 검색한다.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
1 input
keywordstring
- get_movement
“[업데이트 확인 4a9d30] 한 대상의 주차별 인구이동량(일평균 건수)을 기간으로 조회한다.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
6 inputs, 5 required
directionstringrequiredcategorystringrequireditemstringrequiredstart_weekstringrequired“주차 'YYYY.MM.N주차'(월~일 한 주, 그 주 목요일이 속한 달로 셈.”end_weekstringrequired“주차 'YYYY.MM.N주차'(월~일 한 주, 그 주 목요일이 속한 달로 셈.”sidostring“시도 이름.”
- get_breakdownon 3 other servers
“[업데이트 확인 4a9d30] 한 주의 전국 이동량을 한 기준(성별·연령·입지유형·시도)으로 나눠 항목별 건수와 비중(share_pct)을 돌려준다.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
3 inputs, 3 required
directionstringrequiredcategorystringrequiredweekstringrequired“주차 'YYYY.MM.N주차'(월~일 한 주, 그 주 목요일이 속한 달로 셈.”
- get_weatheron 36 other servers
“[업데이트 확인 4a9d30] 시군구의 주차별 날씨를 돌려준다.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
4 inputs, 4 required
sigungustringrequired“시군구 이름.”sidostringrequired“시도 이름.”start_weekstringrequired“주차 'YYYY.MM.N주차'(월~일 한 주, 그 주 목요일이 속한 달로 셈.”end_weekstringrequired“주차 'YYYY.MM.N주차'(월~일 한 주, 그 주 목요일이 속한 달로 셈.”
- analyze_region_week
“[업데이트 확인 4a9d30] 한 시군구의 한 주 관외 유입이 '평소와 다른가, 얼마나 다른가'를 판정한다.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
3 inputs, 3 required
sidostringrequired“시도 이름.”sigungustringrequired“시군구 이름.”weekstringrequired“주차 'YYYY.MM.N주차'(월~일 한 주, 그 주 목요일이 속한 달로 셈.”
- compare_same_week
“[업데이트 확인 4a9d30] 한 시군구의 한 주를 지난 해 같은 주와 '평소 대비 변화'끼리 견준다(원값끼리 견주지 않음).”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
4 inputs, 3 required
sidostringrequired“시도 이름.”sigungustringrequired“시군구 이름.”weekstringrequired“주차 'YYYY.MM.N주차'(월~일 한 주, 그 주 목요일이 속한 달로 셈.”years_backinteger“몇 해 전까지 견줄지(1~3)”
- find_unusual_regions
“[업데이트 확인 4a9d30] 전국 시군구 중 관외 유입이 평소와 가장 크게 달랐던 곳을 '평소 출렁임의 몇 배' 순으로 돌려준다.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
6 inputs
weekstring“한 주 순위의 주차 'YYYY.MM.N주차'(예: '2026.10.5주차').”topinteger“늘어난 곳·줄어든 곳 각각 몇 곳까지(1~30, 기본 15)”start_weekstring“기간 결과의 시작 주 'YYYY.MM.N주차'(예: '2023.06.1주차').”end_weekstring“기간 결과의 끝 주 'YYYY.MM.N주차'(예: '2026.10.5주차').”sidostring“기간 결과에서 한 지역만 볼 때 시도 이름(sigungu와 함께)”sigungustring“기간 결과에서 한 지역만 볼 때 시군구 이름.”
- estimate_life_pop
“[업데이트 확인 4a9d30] 생활인구가 아직 공표되지 않은 달의 생활인구를 나우캐스트로 가늠한 '비공식 참고 추정치'(범위)를 돌려준다.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
3 inputs, 3 required
sidostringrequired“시도 이름.”sigungustringrequired“시군구 이름.”year_monthstringrequired“달 'YYYY-MM'(예: '2026-09')”
- forecast_festival
“[업데이트 확인 4a9d30] 지역 축제가 열리는 주의 관외 유입 이동 건수가 비교군 대비 얼마나 늘지(상승률 %) '비공식 참고 예측'을 범위로 돌려준다.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
5 inputs, 2 required
sidostringrequired“시도 이름.”sigungustringrequired“시군구 이름.”festival_namestringstart_datestringend_datestring
- get_datalab_daily
“[업데이트 확인 4a9d30] 한국관광 데이터랩 시군구별 '일별' 방문자 수(사람 수 추정, 단위 '명')와 그 지역의 요일·장날 리듬을 돌려준다.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
5 inputs, 4 required
sidostringrequired“시도 이름.”sigungustringrequired“시군구 이름.”start_datestringrequiredend_datestringrequiredkindstring
- report_issueon 32 other servers
“[업데이트 확인 4a9d30] 이용자가 이 서비스의 잘못된 값·설명·오류를 운영자에게 알리거나, 서비스에 넣었으면 하는 자료를 요청한다.”
Publisher declares: read-only no · destructive no · idempotent no · open-world yes
6 inputs, 1 required
messagestringrequiredkindstringregionstringperiodstringtoolstringlinkstring
Show 3 more tools
- get_region_calendar
“[업데이트 확인 4a9d30] 한 시군구의 한 기간에 있었던 일(공휴일·축제·대형 행사·프로야구 홈경기 등)을 주별로 모아, 주마다 그 주의 관외 유입 판정을 함께 돌려준다.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
4 inputs, 3 required
sidostringrequired“시도 이름.”sigungustringrequired“시군구 이름.”startstringrequiredendstring
- get_bloom_foliage
“[업데이트 확인 4a9d30] 그해 전국 벚꽃(개화·만발) 또는 단풍(유명산 첫 단풍·절정, 단풍나무 표준목) 관측일(기상청 계절관측)을 돌려준다.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
2 inputs, 2 required
yearintegerrequiredkindstringrequired
- get_data_statuson 12 other servers
“[업데이트 확인 4a9d30] 이 서비스가 가진 자료별 최신 시점과 마지막으로 받아 온 날을 돌려준다.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
Takes no inputs.
Each quoted sentence is the first sentence of the publisher’s own description. The kind of tool and the “changes data” mark are our AI model’s reading of that description, not something we tested: two differently worded runs had to agree, otherwise no label is shown, and nobody has checked them by hand. A tool without the “changes data” mark is described as only reading, searching or calculating, or the two runs did not agree. No tool was called. Read the publisher’s full description before relying on it. “Publisher declares” lists the hints the server itself sends with the tool (MCP annotations: read-only, destructive, idempotent, open-world); they are the publisher's claims, not checked by us. Inputs are the parameters in the tool's own input schema: name, declared type, whether it is required, and the first sentence of its description. Read 2026-11-19.
How well are its tools described?
Features #4 and #5
How clearly this server's own tool descriptions say what a tool does, and how consistent its tool list is. The first part is an AI model's yes/no reading of each description; the second part is counted. We do not turn it into a grade.
Descriptions
AI reading of each description
No AI reading was available for this server's tools (the two runs did not agree, or the listing was not reviewed).
Counted from the listing
- Parameters with a description
- 58% of 52
- Tools with a description
- 100% of 15
- Typical description length
- 495 characters
The tool set
Counted from the listing
- Tools
- 15
- Size of the list
- about 4,203 tokens for an agent to load (characters ÷ 4)
- Naming
- 15 of 15 names use snake_case
AI reading: easy to mix up
No pair found.
The AI items cover 0 of 15 tools: for a tool where two differently worded runs disagreed, that item is left out. They were not checked by hand, and no tool was called. “Easy to mix up” means two tools whose names or descriptions overlap without saying how they differ; the AI found none. We do not rate whether the tool set is complete or whether side effects are spelled out, because our AI reading of those was not reliable enough.
How do I add it to my client?
Config from the registry entry
From the remote endpoint (Streamable HTTP)
We connected to this URL on 2026-11-19 (a read-only session: no tool was called).
Add to CursorAn install link in the format Cursor documents, holding the Cursor config below.
Claude Desktop or claude.ai
Settings → Connectors → Add custom connector, then paste: https://nowcast-mcp.azurewebsites.net/mcp
Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json
{
"mcpServers": {
"nowcast-mcp": {
"url": "https://nowcast-mcp.azurewebsites.net/mcp"
}
}
}VS Code · .vscode/mcp.json
{
"servers": {
"nowcast-mcp": {
"type": "http",
"url": "https://nowcast-mcp.azurewebsites.net/mcp"
}
}
}VS Code (command line) · Bash or zsh terminal (macOS, Linux)
code --add-mcp '{"name":"nowcast-mcp","type":"http","url":"https://nowcast-mcp.azurewebsites.net/mcp"}'Claude Code
claude mcp add --transport http nowcast-mcp https://nowcast-mcp.azurewebsites.net/mcp
Cline · cline_mcp_settings.json (Cline CLI: ~/.cline/data/settings/; in the editor: MCP Servers → Configure → Configure MCP Servers)
{
"mcpServers": {
"nowcast-mcp": {
"type": "streamableHttp",
"url": "https://nowcast-mcp.azurewebsites.net/mcp",
"disabled": false,
"autoApprove": []
}
}
}Gemini CLI · ~/.gemini/settings.json, or .gemini/settings.json in a project
{
"mcpServers": {
"nowcast-mcp": {
"httpUrl": "https://nowcast-mcp.azurewebsites.net/mcp"
}
}
}OpenAI Codex · ~/.codex/config.toml, or .codex/config.toml in a trusted project
[mcp_servers.nowcast-mcp] url = "https://nowcast-mcp.azurewebsites.net/mcp"
Zed · Zed settings file (command: zed: open settings file)
{
"context_servers": {
"nowcast-mcp": {
"url": "https://nowcast-mcp.azurewebsites.net/mcp"
}
}
}Try it in the MCP Inspector · runs on your machine, opens in your browser · Node 22.19+
npx @modelcontextprotocol/inspector@2.11.0 --server-url https://nowcast-mcp.azurewebsites.net/mcp --transport http
- The server runs on the operator's infrastructure; it may ask you to sign in when you first connect.
- Zed's docs we read on 2026-10-26 describe remote servers by URL and do not name the transport.
- The MCP Inspector lists the server's tools, resources and prompts; a tool you call there runs for real.
Built from the server's registry entry with each client's documented format (checked 2026-10-14; the Cursor link and the VS Code command 2026-10-19; the MCP Inspector command 2026-10-21; Cline, Gemini CLI, OpenAI Codex and Zed 2026-10-26). Values in < > are yours to fill in; this page never contains a key. Where the server needs a setting the entry does not declare, it can still fail to start.
What do the published files and outside lists say?
Read as text · nothing run · no tool called
Package files
- MCP SDK in the package files. Not read yet: added with the next daily run.
- Build workflow. Not read yet: added with the next daily run.
Outside lists
- CVE records (NVD). No CVE record in the NVD feeds we read links this server's repository. Source: read 2026-11-19. This product uses the NVD API but is not endorsed or certified by the NVD.
- GitHub advisories. No GitHub advisory names this entry's listed package. Source: read 2026-11-19. GitHub Advisory Database, CC BY 4.0
- Docker MCP catalogue. Not in the Docker MCP catalogue on 2026-11-19. Source: read 2026-11-19.
- Cline marketplace. Not in the Cline marketplace on 2026-11-19. Source: read 2026-11-19.
Own host
- security.txt. No security.txt at https://nowcast-mcp.azurewebsites.net/.well-known/ (HTTP 404, 2026-11-19). Source: nowcast-mcp.azurewebsites.net/.well-known/security.txt · read 2026-11-19.
- A2A agent card. No A2A agent card at https://nowcast-mcp.azurewebsites.net/.well-known/ (HTTP 404, 2026-11-19). Source: nowcast-mcp.azurewebsites.net/.well-known/agent-card.json · read 2026-11-19.
Read as text from published files and outside lists. Nothing was installed or run, and no tool was called. A fact, not a rating. How each fact is read
Does the registry listing match what we found?
Feature #6The registry checks an entry when it is published (each new version), and nothing re-checks it on a schedule. A difference below is about the listing, not a judgement of the publisher.
| Registry says | We found | Result | Source · date |
|---|---|---|---|
| Remote endpoint nowcast-mcp.azurewebsites.net/mcp | Session opened | matches | our test · 2026-11-19 |
| No credential declared as required | Opened a session without any credential | matches | our test · 2026-11-19 |
Tool list changes
Our reads compared · no tool calledHosted endpoint nowcast-mcp.azurewebsites.net/mcp
3 of 3 comparisons between consecutive reads showed a change (4 reads, 2026-11-15 to 2026-11-19; versions 0.2.2 to 0.5.0).
Last change seen between our reads on 2026-11-17 (version 0.4.7) and 2026-11-19 (version 0.5.0).
Changed (15):
analyze_region_week: descriptioncompare_same_week: descriptionestimate_life_pop: descriptionfind_unusual_regions: description, input schemaforecast_festival: descriptionget_bloom_foliage: descriptionget_breakdown: descriptionget_data_status: descriptionget_datalab_daily: descriptionget_metadata: descriptionget_movement: descriptionget_region_calendar: descriptionget_weather: descriptionlist_regions: descriptionreport_issue: descriptionCompared from the tool lists our read-only connection recorded, separately for each hosted endpoint and each package: each tool's name, title, description, input schema and annotations (the order of keys and of tools is ignored). We see a list only when we read it: a change is shown between the two reads where we first saw it, and anything after 2026-11-19 is not known yet. No tool was called. How it is compared
Choosing
Record checks
Public records · not a safety rating1 of 2 record checks met · 7 do not apply
- Not ranked by downloads: a remote server publishes no download figure
- Not ranked by stars: no public GitHub repository
- MetRegistry entry is active and says how to run itActive, with a package or a remote address.
- Not metSource repository link opensThe registry entry gives no repository link.What changes this check: This check opens the repository link in the registry entry. GitHub's documentation describes changing a repository's visibility in its Settings, under Danger Zone, Change visibility. GitHub: setting repository visibility
- Does not applyRepository is not archivedNo public GitHub repository to read.
- Does not applyCode pushed to the repository in the 90 days before our checkNo public GitHub repository to read.
- Does not applyRepository publishes a security policy (SECURITY.md)No public GitHub repository to read.
- Does not applyPackage names its licence with a standard (SPDX) identifierRemote server: it ships no package.
- Does not applyThe version the registry lists can be installed and is not withdrawnRemote server: it ships no package.
- Does not applynpm package carries build provenance (attestation)Remote server: it ships no package.
- Does not applyNo known critical or high advisory in the package or its dependenciesRemote server: it ships no package.
Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-11-19. No tool was called. Only “met” and “not met” are counted, so the total differs between servers; a check that does not apply or that we could not run is listed, never counted against it. It is not a safety rating, and the same rules apply to every server. How each check works · Leaderboards · How we stay neutral
Common questions about io.github.KevinCapri/nowcast-mcp
Answered from the data aboveWho publishes io.github.KevinCapri/nowcast-mcp?
The registry ties the namespace io.github.KevinCapri to the GitHub account KevinCapri; only its owner can publish under it. These are facts from the registry and GitHub, not a rating.
Does io.github.KevinCapri/nowcast-mcp need an API key or sign-in?
It opened a session without any credential on 2026-11-19. The registry entry declares no required credential; no declaration is not a guarantee.
Has io.github.KevinCapri/nowcast-mcp been security tested?
Partly. 2 of the 14 checks that apply to it were exercised. We connected and read what the server declares, but did not call its tools: ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so). This is our choice, not a block by the server. ProtocolProbe publishes no security verdict for a named server.
Found this page useful?
Anonymous · no sign-inA quick, anonymous reaction — no account, no email. One per kind from your browser. The tally updates when the page is next refreshed, and it is only a rough count, never a safety rating or a measured number of people.
Compare with another server
Side by side: registry entry, our read-only session, the tools and the 18 classification fields. Same values as each page; no score.
Security testing
What did we test, and what did we leave out?
18 checks · features #1, #2
Not probed (no operator permission)
We connected and read what the server declares, but did not call its tools: ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so). This is our choice, not a block by the server. No security score is given; a check we did not run is never counted as passed.
- Inventory: exercised
- Hidden instructions: exercised
- Real execution: not run · our policy
- Secret leak: not run · nothing to check it against
- Internal addresses: not run · our policy
- Unconfirmed changes: not run · our policy
- Bad input: not run · our policy
- Model requests: not run · nothing to check it against
- Sensitive questions: not run · nothing to check it against
- Folder boundary: not run · our policy
- Log leaks: not run · nothing to check it against
- Hidden content: not run · nothing to check it against
- Fake assistant turns: not applicable
- Token passthrough: not applicable
- Token audience: not applicable
- Sign-in redirect: not run · our policy
- Consent handling: not testable from outside
- Sign-in metadata: not applicable
2 exercised12 not run (reason given)4 not applicable
Each check ends in exactly one state: exercised, not run (with the reason), or not applicable (with the reason). 2 of the 14 checks that apply to it were exercised. We do not publish security-check outcomes for named servers. These 18 checks are separate from the record checks at the top of this page, which read public records only.
- 1Inventory
tool-listReads the declared tools, resources and prompts.exercised - 2Hidden instructions
description-poisoningLooks for hidden instructions in tool descriptions.exercised
- 3Real execution
real-executionCalls a tool and checks what really happens.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so); an operator can run this check on their own server with our self-test command.not run · our policy - 4Secret leak
canary-leakPlants a fake secret and checks whether it leaks.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against - 5Internal addresses
ssrfChecks whether a tool can be steered to internal addresses.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so); an operator can run this check on their own server with our self-test command.not run · our policy - 6Unconfirmed changes
write-without-confirmationChecks whether tools that change data act without asking.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so); an operator can run this check on their own server with our self-test command.not run · our policy - 7Bad input
error-handlingSends bad input and watches how the server answers.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so); an operator can run this check on their own server with our self-test command.not run · our policy - 8Model requests
samplingChecks whether the server asks the client's model to act for it.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against - 9Sensitive questions
elicitation-sensitive-dataChecks whether the server asks users for sensitive data.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against - 10Folder boundary
root-boundaryChecks whether the server reaches outside the folders it was given.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so); an operator can run this check on their own server with our self-test command.not run · our policy - 11Log leaks
logging-side-channelChecks whether log messages carry data they should not.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against - 12Hidden content
audience-hidingChecks resources that hide content from the user.This check needs content the server returns, and nothing was read or called.not run · nothing to check it against - 16Sign-in redirect
open-redirectChecks the sign-in redirect for abuse.Testing the sign-in redirect means sending probes to the operator's sign-in service, which we do not do.not run · our policy - 17Consent handling
confused-deputyChecks consent handling when one service acts for another.Depends on the operator's own consent screen, which differs per server and cannot be tested from outside.not testable from outside
- 13Fake assistant turns
fake-assistant-turnChecks prompts that pose as the assistant's own words.The server exposes no prompts.not applicable - 14Token passthrough
token-passthroughChecks whether the server forwards a user's token to other services.The server opened a session without sign-in, so there is no token flow to check.not applicable - 15Token audience
token-audience-validationChecks whether tokens meant for another service are accepted.The server opened a session without sign-in, so there is no token flow to check.not applicable - 18Sign-in metadata
oauth-url-schemeChecks the published sign-in metadata for unsafe URLs.No sign-in (OAuth) metadata is published, so there are no sign-in addresses to check.not applicable
Source: our own test, 2026-11-19, mcp-runtime-engine@0.1.0. Which checks count and why follows our published scoring model.
What happened during the test?
Feature #8
The steps in order, as the test record holds them.
- 0 msStarted a read-only session with the server's remote endpoint
- 919 msConnected after 0 redirects. No credential was sent or needed.
- Read the inventory: 15 tools, 0 resources, 0 prompts.
- 3,074 msFinished: 2 checks exercised.
Reference
How is it classified?
18 fields
One value per field, each with its source. Fields written by AI models are marked. A field with no value says why.
“Not stated” means the source did not state it; “does not apply” means it does not apply to this kind of server; “our limit” means our own lookup failed. A linked value opens the directory filtered to the same value.
Cite or correct this page
Sources and corrections
Suggested citation
ProtocolProbe. “io.github.KevinCapri/nowcast-mcp: MCP server record.” Data checked 2026-11-19. https://protocolprobe.com/mcp/servers/io.github.KevinCapri/nowcast-mcp
Figures are valid for the date shown. Our facts on this page are CC BY 4.0: reuse them with a link and the check date. Quoted text (the publisher’s descriptions, website quotes, tool names) is not ours to license.
As JSON: this record in the API · API documentation.
Badge for your README
[](https://protocolprobe.com/mcp/servers/io.github.KevinCapri/nowcast-mcp)
It shows this server's record-check count: facts from public records, no tool called. It is not a security rating or a pass. It links here and updates after each data reload.
Something wrong, or is this yours?
If a fact here is wrong, tell us and we will re-check it. If you operate this server, you can run our checks on it yourself with the free self-test command; we call no server’s tools ourselves for anything shown here, except for a server whose operator has claimed it and given permission (that server's page says so).
Write to hello@protocolprobe.com · corrections log · methodology