Oskkee MCP server
io.github.slavosckie/oskkeeslavosckiestreamable-httpv1.1.0Scanned
Indian creators: free INR rate estimates and audience checks; search with your Oskkee account.
2 tools: 2 change things.
- Reads private data · 0
- Reads text others write · 1
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
2 tools here change things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the Oskkee MCP server can do
The Oskkee MCP server is published by the GitHub account slavosckie. It has 2 tools. It can create or change data (2 tools: estimate_rate and check_creator), but cannot delete data. None of its tools only reads.
1 tool brings in text other people can write (check_creator).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 19, 2026, version 1.1.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
2 tools
Changes things 2Claude Code: ask
check_creatorCheck a social media creator's audience for authenticity signals before working with them: follower quality, engagement patterns, comment authenticity, growth and posting cadence.Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Check a social media creator's audience for authenticity signals before working with them: follower quality, engagement patterns, comment authenticity, growth and posting cadence. Returns an authenticity score (0-100) with the signals behind it and a link to the full public report. Works for Instagram best; YouTube, TikTok and X are read from public data where available. Accounts too small to judge get no score, by design. This is a signal check, not a ruling: "Flagged for review" means look closer, and it is not grounds to call a creator fake. Checks are limited per day; a recent check of the same account is reused for free.
Annotations the server declares
- title: Check a creator's audience
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
estimate_rateEstimate what an Indian Instagram or YouTube creator charges per deliverable, in INR, from their follower count and (optionally) average likes, comments, views and niche.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it Estimate what an Indian Instagram or YouTube creator charges per deliverable, in INR, from their follower count and (optionally) average likes, comments, views and niche. Returns a price per product (Reel, Story, post, package; or YouTube integration, dedicated video, Short) when engagement figures are given, a low-high range when they are not, and the method behind it either way. Uses only the numbers you pass in: it looks nothing up. Accounts below the minimum scale are not priced, and the answer says why.
Annotations the server declares
- title: Estimate a creator's rate (INR)
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write1
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 19, 2026, 17:20 UTC, unchanged since Nov 19, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 2
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- https://oskkee.com/.well-known/oauth-protected-resource
- Authorization servers
- https://oskkee.com
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- yes
- Client ID metadata documents
- no
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 2 tools that change things (2 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://oskkee.com/mcp: tools/list returned 2 tools to an anonymous client, including estimate_rate (write), check_creator (write)
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 1.1.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http oskkee https://oskkee.com/mcpclaude mcp add --transport http oskkee https://oskkee.com/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [],
"ask": [
"mcp__oskkee__estimate_rate",
"mcp__oskkee__check_creator"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as oskkee. Review it before you use it.
Capability tags behind 1 rule
- mcp__oskkee__check_creator untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.github.slavosckie/oskkee/verify?hash=64b1c0d89507f691bee43b2fe90913bfc450108202cd8b482a0c3931cb79db92" | jq -e '.changed == false'Pinned hash 64b1c0d89507, from Nov 19, 2026, 16:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.github.slavosckie/oskkee/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.slavosckie/oskkee)Source: MCP Registry · repository. Synced Nov 19, 2026, 17:18 UTC.
Oskkee MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Oskkee MCP server safe?
- No scan can promise that. What its definitions show: 2 tools, 2 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Oskkee MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Oskkee MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the Oskkee MCP server have?
- 2 tools: 2 write. estimate_rate and check_creator.
Does the Oskkee MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Oskkee MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the Oskkee MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 19, 2026.