upTake MCP server
me.uptake/uptakeuptake.mestreamable-httpv1.1.0Scanned
See which posts, links and releases bring visits, signups and revenue, and draft the next posts.
18 tools: 2 can delete or cancel things, 14 change things and 2 only read.
- Reads private data · 0
- Reads text others write · 3
- Can send data out · 5
- 3 findings
Tools listed without sign-in. Remote posture
With Anlyon
2 tools here can delete or cancel 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 upTake MCP server can do
The upTake MCP server is published by uptake.me, a domain the MCP Registry verified. It has 18 tools. It can delete or cancel things (2 tools: uptake_dismiss_idea and uptake_update_move) and create or change data (14 tools: uptake_projects, uptake_overview, uptake_data, uptake_posts and 10 more). 2 tools only read.
3 tools bring in text other people can write (uptake_setup_status, uptake_get_post and uptake_log_action); 5 tools can send data out of your system (uptake_posts, uptake_edit_post, uptake_write_post and 2 more).
The fixed checks matched 3 findings (tool-shadowing and annotation-conflict). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.
Last scanned Nov 16, 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.
18 tools
Deletes or cancels 2Claude Code: deny
uptake_dismiss_ideaRemoves an idea that does not fit, with a reason; upTake will not suggest it again.No findings
Why it is in this group
- The name "uptake_dismiss_idea" says "dismiss": a word for a change.
- The description's first verb is "remove": a word for removing or ending something.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it Removes an idea that does not fit, with a reason; upTake will not suggest it again.
Annotations the server declares
- title: Dismiss an idea
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: false
- openWorldHint: false
uptake_update_moveMarks one of this week's moves as done (or reopens it), edits its title or reason, dismisses it with a reason, or puts an open move aside for later (snooze).No findings
Why it is in this group
- The name "uptake_update_move" says "update": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it Marks one of this week's moves as done (or reopens it), edits its title or reason, dismisses it with a reason, or puts an open move aside for later (snooze). Only when the maker asks.
Annotations the server declares
- title: Update a move
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: false
- openWorldHint: false
Changes things 14Claude Code: ask
uptake_add_moveAdds a move of the maker's own to this week's list.No findings
Why it is in this group
- The name "uptake_add_move" says "add": a word for a change.
Description, as the server wrote it Adds a move of the maker's own to this week's list.
Annotations the server declares
- title: Add a move
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
uptake_calendarOne week of the calendar: what was published and what it brought, scheduled posts, posts planned for a day (editorial date), and what is left to plan (moments, this week's moves, i…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 One week of the calendar: what was published and what it brought, scheduled posts, posts planned for a day (editorial date), and what is left to plan (moments, this week's moves, ideas).
Annotations the server declares
- title: Calendar
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
uptake_create_linkCreates a tracked link that tells upTake which visits, signups and payments came from where it is shared.No findings
Why it is in this group
- The name "uptake_create_link" says "create": a word for a change.
Description, as the server wrote it Creates a tracked link that tells upTake which visits, signups and payments came from where it is shared.
Annotations the server declares
- title: Create a tracked link
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
uptake_dataOne slice of project data, when the overview is not enough.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 One slice of project data, when the overview is not enough. Slices: channels_90d (visits, signups, revenue and number of posts per source over 90 days); posts_30d (posts of the last 30 days with the visits, signups and revenue each brought); releases_30d (shipped releases and merged changes of the last 30 days (ids usable in uptake_write_post), with their drafts); revenue_by_day_30d (revenue and number of payments per day over 30 days); moments (communication moments: upcoming (ids usable in uptake_write_post), done and skipped); reports_4w (summaries of the last 4 weekly reports and their moves); mentions_7d (what people said about the product in the last 7 days); scheduled_7d (posts scheduled for the next 7 days); time_by_channel_30d (time the maker spent per network over 30 days); google_search_28d (Google Search clicks, impressions and top queries over 28 days); places_28d (results per named place (subreddit, newsletter issue) over 28 days); pages_30d (landing pages over 30 days: visits that entered the site on each page (one person, no pause longer than 30 minutes), signups of those visitors and their signup rate (small_sample under 50 visits)).
Annotations the server declares
- title: Project data
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
uptake_edit_postReplaces the text of one network's version of a post with the maker's own edit, like typing in upTake's Write studio.Can send data outNo findings
Why it is in this group
- The name "uptake_edit_post" says "edit": a word for a change.
What it can reach
- outboundThe name "uptake_edit_post" says "edit" and "post": it writes something other people read.
Description, as the server wrote it Replaces the text of one network's version of a post with the maker's own edit, like typing in upTake's Write studio. Free: no AI, no quota. Refused for a version already published or scheduled, and when the new text drops the tracked link. To rewrite with AI, use uptake_write_post.
Annotations the server declares
- title: Edit a post
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
uptake_ideasOpen post ideas (title, angle, network).1 finding
Why it is in this group
- The description's first verb is "open": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Warn
The server marks "uptake_ideas" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The description's first verb is "open": a word for a change.
Description, as the server wrote it Open post ideas (title, angle, network). Write one with uptake_write_post, about: [{kind: "idea", id}].
Annotations the server declares
- title: Post ideas
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
uptake_link_post_moveMakes a post count for an open move of this week: publishing the post completes the move.Can send data outNo findings
Why it is in this group
- The name "uptake_link_post_move" says "link": a word for a change.
What it can reach
- outboundThe name "uptake_link_post_move" says "link" and "post": it writes something other people read.
Description, as the server wrote it Makes a post count for an open move of this week: publishing the post completes the move.
Annotations the server declares
- title: Link a post to a move
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
uptake_log_actionAdds an action the maker did outside upTake (a post, a newsletter, a talk) to the journal, so upTake measures what it brought.Reads text others writeNo findings
Why it is in this group
- The name "uptake_log_action" says "log": a word for reading.
- The description's first verb is "add": a word for a change.
What it can reach
- untrusted-inputThe description's first sentence says "add" and "post": it reads posts, which other people can write.
Description, as the server wrote it Adds an action the maker did outside upTake (a post, a newsletter, a talk) to the journal, so upTake measures what it brought.
Annotations the server declares
- title: Log an action
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
uptake_more_ideasAsks upTake for a new series of post ideas from the project's data.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.
Description, as the server wrote it Asks upTake for a new series of post ideas from the project's data. Counts against the maker's monthly idea series.
Annotations the server declares
- title: New post ideas
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
uptake_overviewThe project at a glance: product, stage and goal, this week's visits, signups, paying customers and revenue against the 4 previous weeks (small_sample when a % change rests on too …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 The project at a glance: product, stage and goal, this week's visits, signups, paying customers and revenue against the 4 previous weeks (small_sample when a % change rests on too little data), top sources over 30 days, last actions and what they brought (tracked_link: false means estimated numbers), this week's moves, the next communication moment, the last weekly report. Empty fields say what to set up and where. Start here.
Annotations the server declares
- title: Project overview
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
uptake_plan_postSets or clears the day a post is planned for in the calendar.Can send data outNo findings
Why it is in this group
- The name "uptake_plan_post" says "post": a word for a change.
What it can reach
- outboundThe name "uptake_plan_post" says "post": it sends or publishes something to other people.
Description, as the server wrote it Sets or clears the day a post is planned for in the calendar. Only the editorial date: nothing is scheduled or sent.
Annotations the server declares
- title: Plan a post
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
uptake_postsPosts prepared in upTake's Write studio, with their state (Draft, Planned, Scheduled, Published…), networks and link to open them.Can send data out1 finding
Why it is in this group
- The name "uptake_posts" says "post": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- outboundThe name "uptake_posts" says "post": it sends or publishes something to other people.
Findings
- Warn
The server marks "uptake_posts" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "uptake_posts" says "post": a word for a change.
Description, as the server wrote it Posts prepared in upTake's Write studio, with their state (Draft, Planned, Scheduled, Published…), networks and link to open them.
Annotations the server declares
- title: Posts in Write
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
uptake_projectsThe maker's projects (id, name, site).1 finding
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.
Findings
- Warn
The description contains "Every other tool", wording about other tools or servers.
What this check looks forMatched text
description: "The maker's projects (id, name, site). Every other tool takes `project`: call this first when t..."
Description, as the server wrote it The maker's projects (id, name, site). Every other tool takes `project`: call this first when the maker has several.
Annotations the server declares
- title: Projects
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
uptake_write_postPrepares a post in upTake's Write studio, in the maker's voice and with tracked links, and returns the text for each network.Can send data outNo findings
Why it is in this group
- The name "uptake_write_post" says "write": a word for a change.
What it can reach
- outboundThe name "uptake_write_post" says "write" and "post": it writes something other people read.
Description, as the server wrote it Prepares a post in upTake's Write studio, in the maker's voice and with tracked links, and returns the text for each network. Nothing is published or scheduled: the maker reviews and sends it from upTake. Counts against the maker's monthly drafts (a rewrite when the network already has a version). Takes up to a minute.
Annotations the server declares
- title: Write a post
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
Only reads 2Show 2 read-only tools
uptake_get_postOne post by its id: the current version for each of its networks, whether it is posted, and whether it carries a tracked link.Reads text others writeNo findings
Why it is in this group
- The name "uptake_get_post" says "get": a word for reading.
What it can reach
- untrusted-inputThe name "uptake_get_post" says "get" and "post": it reads posts, which other people can write.
- untrusted-inputThe description's first sentence says "post": it reads posts, which other people can write.
Description, as the server wrote it One post by its id: the current version for each of its networks, whether it is posted, and whether it carries a tracked link.
Annotations the server declares
- title: Read a post
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
uptake_setup_statusChecks that tracking works before reading a 0: is the website script receiving visits, do signups and payments reach upTake, do posts carry tracked links, and is the weekly report …Reads text others writeNo findings
Why it is in this group
- The name "uptake_setup_status" says "status": a word for reading.
What it can reach
- untrusted-inputThe description's first sentence says "website": it reads web pages, which anyone can write.
Description, as the server wrote it Checks that tracking works before reading a 0: is the website script receiving visits, do signups and payments reach upTake, do posts carry tracked links, and is the weekly report being sent. Each check says ok, warn or missing, why, and where to fix it.
Annotations the server declares
- title: Tracking health
- 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.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write3
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out5
- 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 17, 2026, 15:23 UTC, unchanged since Nov 3, 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
- 16
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- https://uptake.me/.well-known/oauth-protected-resource/api/mcp
- Authorization servers
- https://uptake.me
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- yes
- Client ID metadata documents
- no
- HighThe whole server
The endpoint served tools/list without credentials, and the list has 16 tools that change things (2 destructive, 14 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://uptake.me/api/mcp: tools/list returned 18 tools to an anonymous client, including uptake_dismiss_idea (destructive), uptake_update_move (destructive), uptake_projects (write), uptake_overview (write), uptake_data (write) and 11 more
Findings
Matches of fixed checks, with the text they matched.
- Warnuptake_projects
The description contains "Every other tool", wording about other tools or servers.
What this check looks forMatched text
description: "The maker's projects (id, name, site). Every other tool takes `project`: call this first when t..."
- Warnuptake_posts
The server marks "uptake_posts" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "uptake_posts" says "post": a word for a change.
- Warnuptake_ideas
The server marks "uptake_ideas" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The description's first verb is "open": a word for a change.
History
Changes to its tool definitions and to its remote endpoint, newest first.
Tools3 added, 1 removed, 3 changed.+3 added−1 removed~3 changedView diff
- Added:uptake_edit_postChanges things
- Added:uptake_get_postOnly reads
- Added:uptake_setup_statusOnly reads
- Removed:uptake_post
- Changed:uptake_dataChanges thingsdescriptioninputSchema
- Changed:uptake_overviewChanges thingsdescription
- Changed:uptake_update_moveDeletes or cancelsdescriptioninputSchema
Install
Pinned to version 1.1.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http uptake https://uptake.me/api/mcpclaude mcp add --transport http uptake https://uptake.me/api/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": [
"mcp__uptake__uptake_setup_status",
"mcp__uptake__uptake_get_post"
],
"ask": [
"mcp__uptake__uptake_projects",
"mcp__uptake__uptake_overview",
"mcp__uptake__uptake_data",
"mcp__uptake__uptake_posts",
"mcp__uptake__uptake_edit_post",
"mcp__uptake__uptake_write_post",
"mcp__uptake__uptake_create_link",
"mcp__uptake__uptake_log_action",
"mcp__uptake__uptake_calendar",
"mcp__uptake__uptake_ideas",
"mcp__uptake__uptake_more_ideas",
"mcp__uptake__uptake_add_move",
"mcp__uptake__uptake_plan_post",
"mcp__uptake__uptake_link_post_move"
],
"deny": [
"mcp__uptake__uptake_dismiss_idea",
"mcp__uptake__uptake_update_move"
]
}
}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 uptake. Review it before you use it.
Capability tags behind 8 rules
- mcp__uptake__uptake_setup_status untrusted-input
- mcp__uptake__uptake_posts outbound
- mcp__uptake__uptake_get_post untrusted-input
- mcp__uptake__uptake_edit_post outbound
- mcp__uptake__uptake_write_post outbound
- mcp__uptake__uptake_log_action untrusted-input
- mcp__uptake__uptake_plan_post outbound
- mcp__uptake__uptake_link_post_move outbound
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/me.uptake/uptake/verify?hash=8c90de0e05315ec1997a06d01f741f01b84658540f45e62ad84107cc74cc817a" | jq -e '.changed == false'Pinned hash 8c90de0e0531, from Nov 16, 2026, 22:17 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/me.uptake/uptake/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/me.uptake/uptake)Source: MCP Registry. Synced Nov 3, 2026, 10:18 UTC.
upTake MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the upTake MCP server safe?
- No scan can promise that. What its definitions show: 18 tools, 16 of which can change, send or delete something, and 3 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 upTake MCP server delete data?
- Yes. 2 tools can delete, cancel or revoke something: uptake_dismiss_idea and uptake_update_move.
Can the upTake 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 upTake MCP server have?
- 18 tools: 2 destructive, 14 write, 2 read. uptake_dismiss_idea, uptake_update_move, uptake_projects, uptake_overview, uptake_data, uptake_posts, uptake_edit_post, uptake_write_post and 10 more.
Does the upTake MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the upTake MCP server send data to outside services?
- 5 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): uptake_posts, uptake_edit_post, uptake_write_post, uptake_plan_post and uptake_link_post_move.
Has the upTake MCP server changed its tools?
- Yes, once since Anlyon Radar started tracking it, most recently on Nov 16, 2026. Every change is on this page and in its Atom feed.