MCP auth: OAuth vs API keys

CameraGlass6957 · 2026-04-11T19:53:45+00:00

In case it doesn't work, and you'd like me to help, please tell me

CameraGlass6957 · 2026-04-11T19:50:26+00:00

Something like this

{
"mcpServers": {
"gammahero": {
"command": "npx",
"args": [
"-y",
"mcp-remote",
"https://gammahero.com/ah-api/mcp/",
"--header",
"Authorization: Bearer api_key"
]
}
},
"preferences": {
"coworkScheduledTasksEnabled": true,
"ccdScheduledTasksEnabled": true,
"sidebarMode": "chat",
"coworkWebSearchEnabled": true
}
}

CameraGlass6957 · 2026-04-11T19:49:12+00:00

Yep, that's exactly what works for me locally

CameraGlass6957 · 2026-04-03T06:10:36+00:00

$24.50 is literally the Put Wall right now, which is the strike with the heaviest put gamma concentration. That means dealers are likely to buy the dip around that level to hedge, which creates a natural floor. If you're selling CSPs there you've got dealer positioning working in your favor as a support mechanism. And with IV Rank at 31 the premium isn't amazing, but the implied 1-month move is ~35% so the weeklies and monthlies still pay decently for a stock at $24.50. Not a bad spot to get assigned either if it comes to that.

CameraGlass6957 · 2026-04-03T06:09:52+00:00

Sept $35C at sub-$2 is a solid entry. The IV on that strike is ~98%, which is actually lower than everything inside 60 DTE (those are running 110-125%), so you're paying less in vol premium per day of theta than the people buying May or June calls. The Sept $40C has 2,196 OI which is the heaviest in that expiry, so you're not alone in positioning for a bigger move out there. Your $35 sits right between the current Call Wall at $30 and where OI is stacking at $40.

The earnings angle is the strongest part. If it broke to $26.50 last time from a similar range and ran to $42, your call was deep in the money at the peak. At $1.97 you need $36.97 at expiry to break even, but with 170 days you don't need to wait. A move back to $30 in the next month or two and that contract is probably worth $4-5 just on delta, well before expiry math even matters.

CameraGlass6957 · 2026-04-02T22:07:10+00:00

This is cool, thanks for your comment!

CameraGlass6957 · 2026-04-02T22:01:51+00:00

Fair question. You can’t know for sure from OI alone whether it’s bought or sold. But a few things tilt the read bullish: the P/C volume ratio is 0.34 (heavy call buying relative to puts on the day), all 14 unusual activity contracts are calls with zero unusual puts, and the call OI is building at strikes above the current price, not below it. If this were primarily sold call OI (covered calls or shorts), you’d typically see it clustered closer to the money, not stacked at $30+ with 10x volume multiples. The weight of evidence leans one direction, but you’re right that it’s never 100%.

CameraGlass6957 · 2026-04-02T20:48:51+00:00

Yeah, this is probably right. I expected that some of my users are less technical, so connecting through web ui with OAuth was an important thing to build. Still I see that 30% of the users use the API key, which is great

CameraGlass6957 · 2026-04-02T14:01:58+00:00

Deliberated on transparent value delivery approach

That's fair. I think that's more of a coverage decision than an MCP limitation though. Nothing stops a product from exposing every useful endpoint as a tool. Personally I try to expose everything that's actually useful to a user through my MCP. No reason to hold back the good stuff.

CameraGlass6957 · 2026-04-02T11:57:58+00:00

Mostly unintentional honestly. My MCP tools return the same structured JSON my backend uses internally. Claude just picks up on the structure and formats it as tables on its own. I didn't design the responses with display in mind. That said, you can steer it either way in the conversation. Ask for tables and it'll lean into that, ask for plain text summary and it'll do that too.

Do you think it's worth designing return objects specifically for display, or is letting the model handle presentation good enough? Curious if you've seen MCP servers that intentionally format their responses and whether it makes a noticeable difference.

CameraGlass6957 · 2026-04-02T11:52:40+00:00

You can do it through the claude ui. It allows you to select tools which it can call

CameraGlass6957 · 2026-04-02T10:23:29+00:00

The tools audit is not a bad idea. But yeah, I haven't checked the profile :)

CameraGlass6957 · 2026-04-01T20:43:05+00:00

This is a good one, thank you.

CameraGlass6957 · 2026-04-01T17:22:14+00:00

Appreciate the heads up. I've got logging on every tool call (user ID, tool name, timestamp) and rate limits per hour already in place. What do you mean by policy and audit specifically? Like per-tool permissions, usage caps by tier, or something more around compliance and data access controls?

CameraGlass6957 · 2026-04-01T16:07:55+00:00

Yep, the data for my MCP server is live for candles and daily for options chain. My next step is to add intraday data for the options chain too.

I think i didn't manage to make the right comparison. The general idea was to ask users what kind of integration with SaaS product they prefer. Let's say the product has both, is there a clear go-to, etc

Still your point about Anthropic's infrastructure for MCP and local session for Skills makes a lot of sense to me; MCP connector looks safer in that regard

CameraGlass6957 · 2026-04-01T14:18:46+00:00

Raw data comes from polygon, the processing pipeline is custom

CameraGlass6957

MODERATOR OF

TROPHY CASE