mlenhard

6 ms·

1.
The AI Account Reseller Ecosystem(vectoral.com)
2 points by mlenhard 11d ago|0 comments
2.
The Chinese wholesale market for Claude and ChatGPT accounts(vectoral.com)
3 points by mlenhard 14d ago|0 comments
3.
by mlenhard 1mo ago
I don't have exact numbers here, and it varies by company, but a rough guess is around 10-20%. This might be a bit biased because the companies willing to talk to me are probably seeing the worst of it. Also, outside the labs, most of
4.
by mlenhard 1mo ago
This was poorly worded on my part; I meant in terms of dollars, not tokens.
5.
by mlenhard 1mo ago
From talking with some of the companies experiencing this, I can confirm that a portion of it is actual credit card fraud. Tokens have become a pseudo-currency, making them a prime target for abuse. Some of the abuse is more benign, but the
6.
by mlenhard 1mo ago
This was specifically meant to be about the ai credit resellers, not the relays themselves. I put together another piece here: https://vectoral.com/blog/token-relay-market that tackles that side of the market.
7.
The AI Credit Resale Economy(vectoral.com)
334 points by mlenhard 1mo ago|130 comments
8.
Who Are the Token Brokers?(vectoral.com)
3 points by mlenhard 1mo ago|0 comments
9.
by mlenhard 2mo ago
I don't think device fingerprinting is the right approach here. Client-side detection can always be sidestepped, and you need to intermediate the actual inference to get enough signals to make an accurate prediction. There are hundreds
10.
by mlenhard 2mo ago
I was going to cover this in a follow-up article, but yeah, there are network of token brokers who buy unused credits from startups and then resell them.
11.
by mlenhard 2mo ago
Yeah, I should probably clean this up. The sentence is a bit hard to understand. What I was trying to show was the steep discounts offered by resellers.
12.
The relay market powering token resellers and fraud(vectoral.com)
209 points by mlenhard 2mo ago|136 comments
13.
Evolving OAuth Client Registration in the Model Context Protocol(blog.modelcontextprotocol.io)
1 points by mlenhard 1y ago|0 comments
14.
Monkey Patching Otel and Prometheus Support into MCP(mcpevals.io)
1 points by mlenhard 1y ago|0 comments
15.
by mlenhard 1y ago
I actually came across Plandex the other day. I haven't had the chance to play around with it yet, but it looked really cool. But agree that even basic prompts can be a struggle. You often need to name the tool in the prompt to get thi
16.
by mlenhard 1y ago
Agree on the unpredictability of results issue. Tool call selection is still sort of a black box. How do you know what variations of a prompt trigger a given tool to be called or how many tools is too many before you start seeing degradatio
17.
Tools vs. Agents: A Mathematical Framework(mcpevals.io)
2 points by mlenhard 1y ago|0 comments
18.
Show HN: Open-source load balancer for distributed MCP server architecture(github.com)
2 points by mlenhard 1y ago|0 comments
19.
by mlenhard 1y ago
This is pretty cool. You should also attempt to scan resources if possible. Similar to the tool injection attack Invariant Labs discovered, I achieved the same result via resource injection [1]. The three things I want solved to improve loc
20.
by mlenhard 1y ago
Yeah, you aren't far off with SQL injection comparison. That being said it's not really a fault of the MCP spec, more so with current client implementations of it.
21.
by mlenhard 1y ago
One of the biggest issues I see, briefly discussed here, is how one MCP server tool's output can affect other tools later in the same message thread. To prevent this, there really needs to be sandboxing between tools. Invariant labs di
22.
MCP Resource Poisoning Prompt Injection Attacks(bernardiq.com)
5 points by mlenhard 1y ago|0 comments
23.
by mlenhard 1y ago
Yeah, I plan on improving the formatting and adding a few more examples. There were even still some typos in the piece. To be honest, I didn't plan on sharing it yet; I just figured it might be helpful for the OP, so I shared it early.
24.
by mlenhard 1y ago
Yeah, at its core it's just a proxy, so there are a lot of other tools out there that would do the job. It does have a nice UI and I try to support projects like it when I can. I'll check out your proxy as well, I enjoy looking at
25.
by mlenhard 1y ago
I was in the same boat in regards to trying to find the actual JSON that was going over the wire. I ended up using Charles to capture all the network requests. I haven't finished the post yet, but if you want to see the actual JSON I
26.
by mlenhard 2y ago
super cool. Debugging locally across multiple microservices can be a huge pain. A small feature request/idea - packaging this as a helm chart to make local development on something like Minkikube easier.
27.
by mlenhard 3y ago
Congrats on the 1.0 Release, big milestone. I'm personally really excited about all of the recent tooling for postgres aggregates. Definitely a pain point for a lot of developers and its easy to fall in trap where things work fine in t
28.
by mlenhard 3y ago
Congrats on the launch! For those who have not experimented with columnar based databases, I would highly recommend toying around with them. The performance improvements can be substantial. Obviously there are drawbacks involved with integr
29.
Building an eBPF Based Profiler(containiq.com)
12 points by mlenhard 4y ago|0 comments
30.
Decrypting SSL at scale with eBPF, libbpf and K8s(containiq.com)
10 points by mlenhard 4y ago|6 comments

More ›